Method to protect software against unwanted use with a &#39;&#39;detection and coercion&#39;&#39; principle

ABSTRACT

The invention concerns a process to protect a vulnerable software working on a data processing system against its unauthorized usage using a processing and memorizing unit. The process comprises defining: 1) at least one software execution characteristic, liable to be monitored at least in part in a processing and memorizing unit 2) at least one criterion to abide by for at least one software execution characteristic 3) detection means to implement in a processing and memorizing unit and enabling to detect that at least one software execution characteristic does not abide by at least one associated criterion 4) coercion means to implement in a processing and memorizing unit and enabling to inform the data processing system and/or modify the execution of a software when at least one criterion is not abided by.

BACKGROUND OF THE INVENTION

[0001] This invention concerns the technical domain of data processing systems in the general sense, and is more precisely aimed at the means of protecting software running on said data processing systems against unauthorized usage.

[0002] The subject of the invention aims in particular at the means of protecting software against unauthorized usage, using a processing and memorizing unit, such a unit being commonly materialized by a chip card or a material key on USB port.

[0003] In the technical domain above, the main problem concerns the unauthorized usage of software by users who have not paid the license rights. This illicit use of software causes an obvious loss for software editors, software distributors and/or any person integrating such software in products. To avoid such illicit copies, various solutions, in the state of technology, have been proposed to protect software.

[0004] Thus, a protection solution is known, which makes use of a hardware protection system, such as a physical component named protection key or “dongle”. Such a protection key should guarantee that the software executes only in presence of the key. Yet, it must be acknowledged that this solution is ineffective because it presents the inconvenience of being easy to bypass. An ill-intentioned person or a hacker can, with the aid of specialized tools such as disassemblers, delete the control instructions of the protection key. It becomes then possible to make illicit copies corresponding to modified versions of the software able to run without the protection. Moreover, this solution cannot be generalized to all software, inasmuch as it is difficult to connect more than two protection keys to the same system.

BRIEF SUMMARY OF THE INVENTION

[0005] The subject of the invention aims precisely at finding a solution to the aforementioned problems by proposing a process to protect a software against unauthorized usage, using an ad hoc processing and memorizing unit, inasmuch as the presence of such a unit is necessary for the software to be completely functional.

[0006] So as to reach such a goal, the subject of the invention concerns a process to protect, using at least one blank unit including at least processing means and memorization means, a vulnerable software against its unauthorized usage, said vulnerable software being produced from a source and working on a data processing system. The process according to the invention comprises:

[0007] during a protection phase:

[0008] defining:

[0009] at least one software execution characteristic, liable to be monitored at least in part in a unit,

[0010] at least one criterion to abide by for at least one software execution characteristic,

[0011] detection means to implement in a unit and enabling to detect that at least one software execution characteristic does not abide by at least one associated criterion,

[0012] and coercion means to implement in a unit and enabling to inform the data processing system and/or modify the execution of a software when at least one criterion is not abided by,

[0013] constructing exploitation means enabling to transform the blank unit into a unit able to implement the detection means and the coercion means,

[0014] creating a protected software:

[0015] by choosing at least one software execution characteristic to monitor, among the software execution characteristics liable to be monitored,

[0016] by choosing at least one criterion to abide by for at least one chosen software execution characteristic,

[0017] by choosing, at least one algorithmic processing which, during the execution of the vulnerable software, uses at least one operand and enables to obtain at least one result, and for which at least one chosen software execution characteristic, is to be monitored,

[0018] by choosing at least one portion of the source of the vulnerable software containing, at least one chosen algorithmic processing,

[0019] by producing the source of the protected software from the source of the vulnerable software, by modifying at least one chosen portion of the source of the vulnerable software to obtain at least one modified portion of the source of the protected software, this modification being such that:

[0020] during the execution of the protected software a first execution part is executed in the data processing system and a second execution part is executed in a unit, obtained from the blank unit after upload of information,

[0021] the second execution part executes at least the functionality of at least one chosen algorithmic processing,

[0022] and during the execution of the protected software, at least one chosen execution characteristic is monitored by means of the second execution part and the fact that a criterion is not abided by leads to a modification of the execution of the protected software,

[0023] and by producing:

[0024] a first object part of the protected software, from the source of the protected software, said first object part being such that during the execution of the protected software, appears a first execution part which is executed in the data processing system and whose at least a portion takes into account that at least one chosen software execution characteristic is monitored,

[0025] and a second object part of the protected software, containing the exploitation means implementing the detection means and the coercion means, said second object part being such that, after upload to the blank unit and during the execution of the protected software, appears the second execution part by means of which at least one chosen software execution characteristic is monitored and by means of which the fact that a criterion is not abided by leads to a modification of the execution of the protected software,

[0026] and uploading the second object part to the blank unit, with the intention of obtaining the unit,

[0027] and during a usage phase during which the protected software is executed:

[0028] in the presence of the unit:

[0029] and as long as all the criteria corresponding to all the monitored execution characteristics of all the modified portions of the protected software are abided by, enabling said portions of the protected software to work nominally and consequently enabling the protected software to work nominally,

[0030] and if at least one of the criteria corresponding to a monitored execution characteristic of a portion of the protected software is not abided by, informing the data processing system of it and/or modifying the functioning of the portion of the protected software, so that the functioning of the protected software is modified,

[0031] and in the absence of the unit, in spite of the request by a portion of the first execution part to trigger the execution in the unit, of the functionality of a chosen algorithmic processing, in not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently, the protected software is not completely functional.

[0032] According to a variant embodiment, the process according to the invention comprises:

[0033] during the protection phase:

[0034] defining:

[0035] as software execution characteristic liable to be monitored, a variable of measurement of the usage of a functionality of a software,

[0036] as criterion to abide by, at least one threshold associated to each variable of measurement,

[0037] and actualization means enabling to update at least one variable of measurement,

[0038] constructing the exploitation means enabling the unit to also implement the actualization means,

[0039] and modifying the protected software:

[0040] by choosing as software execution characteristic to monitor, at least one variable of measurement of the usage of at least one functionality of a software,

[0041] by choosing:

[0042] at least one functionality of the protected software whose usage is liable to be monitored using a variable of measurement,

[0043] at least one variable of measurement used to quantify the usage of said functionality,

[0044] at least one threshold associated to a chosen variable of measurement corresponding to a limit of usage of said functionality,

[0045] and at least one method of update of a chosen variable of measurement depending on the usage of said functionality,

[0046] and by modifying at least one chosen portion of the source of the protected software, this modification being such that, during the execution of the protected software, the variable of measurement is actualized by means of the second execution part depending on the usage of said functionality, and at least one threshold crossing is taken into account,

[0047] and during the usage phase, in the presence of the unit, and in the case where at least one threshold crossing corresponding to at least one limit of usage is detected, informing the data processing system of it and/or modifying the functioning of the portion of the protected software, so that the functioning of the protected software is modified.

[0048] According to a variant embodiment, the process according to the invention comprises:

[0049] during the protection phase:

[0050] defining:

[0051] for at least one variable of measurement, several associated thresholds,

[0052] and different coercion means corresponding to each of said thresholds,

[0053] and modifying the protected software:

[0054] by choosing in the source of the protected software, at least one chosen variable of measurement to which must be associated several thresholds corresponding to different limits of usage of the functionality,

[0055] by choosing at least two thresholds associated to the chosen variable of measurement,

[0056] and by modifying at least one chosen portion of the source of the protected software, this modification being such that, during the execution of the protected software, the crossings of the various thresholds are taken into account differently, by means of the second execution part,

[0057] and during the usage phase:

[0058] in the presence of the unit:

[0059] in the case where the crossing of a first threshold is detected, enjoining the protected software not to use the corresponding functionality anymore,

[0060] and in the case where the crossing of a second threshold is detected, making ineffective the corresponding functionality and/or at least one portion of the protected software.

[0061] According to a variant embodiment, the process according to the invention comprises:

[0062] during the protection phase:

[0063] defining refilling means enabling to credit at least one software functionality monitored by a variable of measurement with at least one additional usage,

[0064] constructing the exploitation means also allowing the unit to implement the refilling means,

[0065] and modifying the protected software:

[0066] by choosing in the source of the protected software, at least one chosen variable of measurement enabling to limit the usage of a functionality and which must be able to be credited with at least one additional usage,

[0067] and by modifying at least one chosen portion, this modification being such that during a phase called of refilling, at least one additional usage of at least one functionality corresponding to a chosen variable of measurement can be credited,

[0068] and during the phase of refilling:

[0069] reactualizing at least one chosen variable of measurement and/or at least one associated threshold, so as to allow at least one additional usage of the functionality.

[0070] According to a variant embodiment, the process according to the invention comprises:

[0071] during the protection phase:

[0072] defining:

[0073] as software execution characteristic liable to be monitored, a profile of software usage,

[0074] and as criterion to abide by, at least one feature of software execution,

[0075] and modifying the protected software:

[0076] by choosing as software execution characteristic to monitor at least one profile of software usage,

[0077] by choosing at least one feature of execution by which at least one chosen profile of usage must abide,

[0078] and by modifying at least one chosen portion of the source of the protected software, this modification being such that, during the execution of the protected software, the second execution part abides by all the chosen features of execution,

[0079] and during the usage phase in the presence of the unit, and in the case where it is detected that at least one feature of execution is not abided by, informing the data processing system of it and/or modifying the functioning of the portion of the protected software, so that the functioning of the protected software is modified.

[0080] According to a variant embodiment, the process according to the invention comprises:

[0081] during the protection phase:

[0082] defining:

[0083] an instructions set whose instructions are liable to be executed in the unit,

[0084] a set of instructions commands for said instructions set, said instructions commands being liable to be executed in the data processing system and to trigger in the unit the execution of the instructions,

[0085] as profile of usage, the chaining of the instructions,

[0086] as feature of execution, an expected chaining for the execution of the instructions,

[0087] as detection means, means enabling to detect that the chaining of the instructions does not correspond to the expected one,

[0088] and as coercion means, means enabling to inform the data processing system and/or to modify the functioning of the portion of protected software when the chaining of the instructions does not correspond to the expected one,

[0089] constructing the exploitation means also enabling the unit to execute the instructions of the instructions set, the execution of said instructions being triggered by the execution in the data processing system, of the instructions commands,

[0090] and modifying the protected software:

[0091] by modifying at least one chosen portion of the source of the protected software, this modification being such that:

[0092] at least one chosen algorithmic processing is split so that during the execution of the protected software, said algorithmic processing is executed by means of the second execution part, using instructions,

[0093] for at least one chosen algorithmic processing, instructions commands are integrated to the source of the protected software, so that during the execution of the protected software, each instruction command is executed by the first execution part and triggers in the unit, the execution by means of the second execution part, of an instruction,

[0094] a sequence of the instructions commands is chosen among the set of sequences allowing the execution of the protected software,

[0095] and the chaining by which must abide at least some of the instructions during their execution in the unit is specified,

[0096] and during the usage phase, in the presence of the unit, in the case where it is detected that the chaining of the instructions executed in the unit does not correspond to the expected one, informing the data processing system of it and/or modifying the functioning of the portion of the protected software, so that the functioning of the protected software is modified.

[0097] According to a variant embodiment, the process according to the invention comprises:

[0098] during the protection phase:

[0099] defining:

[0100] as instructions set, an instructions set whose at least some instructions work with registers and use at least one operand with the intention of returning a result,

[0101] for at least some of the instructions working with registers:

[0102] a part defining the functionality of the instruction,

[0103] and a part defining the expected chaining for the execution of the instructions and including bits fields corresponding to:

[0104] an identification field of the instruction,

[0105] and for each operand of the instruction:

[0106] a flag field,

[0107] and an expected identification field of the operand,

[0108] for each register belonging to the exploitation means and used by the instructions set, a generated identification field in which is automatically memorized the identification of the last instruction which has returned its result in said register,

[0109] as detection means, means enabling, during the execution of an instruction, for each operand, when the flag field imposes it, to check the equality of the generated identification field corresponding to the register used by said operand, and the expected identification field of the origin of said operand,

[0110] and as coercion means, means enabling to modify the result of the instructions, if at least one of the checked equalities is false.

[0111] According to a preferred embodiment, the process according to the invention comprises:

[0112] during the protection phase:

[0113] modifying the protected software:

[0114] by choosing at least one variable used in at least one chosen algorithmic processing, which during the execution of the protected software, partially defines the state of the protected software,

[0115] by modifying at least one chosen portion of the source of the protected software, this modification being such that during the execution of the protected software, at least one chosen variable or at least one copy of chosen variable resides in the unit,

[0116] and by producing:

[0117] the first object part of the protected software, said first object part being such that during the execution of the protected software, at least one portion of the first execution part takes also into account that at least one variable or at least one copy of variable resides in the unit,

[0118] and the second object part of the protected software, said second object part being such that, after upload to the unit and during the execution of the protected software, appears the second execution part by means of which at least one chosen variable, or at least one copy of chosen variable resides too in the unit,

[0119] and during the usage phase:

[0120] in the presence of the unit each time a portion of the first execution part imposes it, using a variable or a copy of variable residing in the unit, so that said portion is executed correctly and that, consequently, the protected software is completely functional,

[0121] and in the absence of the unit, in spite of the request by a portion of the first execution part to use a variable or a copy of variable residing in the unit, not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently the protected software is not completely functional.

[0122] According to another preferred embodiment, the process according to the invention comprises:

[0123] during the protection phase:

[0124] defining:

[0125] as a triggering command, an instruction command,

[0126] as a dependent function, an instruction,

[0127] as an order, at least one argument for a triggering command, corresponding at least in part to the information transmitted by the data processing system to the unit, so as to trigger the execution of the corresponding dependent function,

[0128] a method of renaming of the orders enabling to rename the orders so as to obtain triggering commands with renamed orders,

[0129] and restoring means designed to be used in the unit during the usage phase, and enabling to restore the dependent function to execute, from the renamed order,

[0130] constructing exploitation means enabling the unit to also implement the restoring means,

[0131] and modifying the protected software:

[0132] by choosing in the source of the protected software, triggering commands,

[0133] by modifying at least one chosen portion of the source of the protected software by renaming the orders of the chosen triggering commands, so as to conceal the identity of the corresponding dependent functions,

[0134] and by producing:

[0135] the first object part of the protected software, said first object part being such that during the execution of the protected software, the triggering commands with renamed orders are executed,

[0136] and the second object part of the protected software containing the exploitation means also implementing the restoring means, said second object part being such that, after upload to the unit and during the execution of the protected software, the identity of the dependent functions whose execution is triggered by the first execution part is restored by means of the second execution part, and the dependent functions are executed by means of the second execution part,

[0137] and during the usage phase:

[0138] in the presence of the unit and each time a triggering command with renamed order, contained in a portion of the first execution part imposes it, restoring in the unit, the identity of the corresponding dependent function and executing it, so that said portion is executed correctly and that, consequently, the protected software is completely functional,

[0139] and in the absence of the unit, in spite of the request by a portion of the first execution part, to trigger the execution of a dependent function in the unit, not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently, the protected software is not completely functional.

[0140] According to a variant embodiment, the process according to the invention comprises:

[0141] during the protection phase:

[0142] defining for at least one dependent function, a family of dependent functions algorithmically equivalent, but triggered by triggering commands whose renamed orders are different,

[0143] and modifying the protected software:

[0144] by choosing, in the source of the protected software at least one triggering command with renamed order,

[0145] and by modifying at least one chosen portion of the source of the protected software by replacing at least the renamed order of one chosen triggering command with renamed order, with another renamed order, triggering a dependent function of the same family.

[0146] According to a variant embodiment, the process according to the invention comprises:

[0147] during the protection phase, defining, for at least one dependent function, a family of algorithmically equivalent dependent functions:

[0148] by concatenating a field of noise to the information defining the functional part of the dependent function to execute in the unit,

[0149] or by using the identification field of the instruction and the expected identification fields of the operands.

[0150] According to a variant embodiment, the process according to the invention comprises:

[0151] during the protection phase:

[0152] defining:

[0153] as method of renaming of the orders, a ciphering method to cipher the orders,

[0154] and as restoring means, means implementing a deciphering method to decipher the renamed orders and thus restore the identity of the dependent functions to execute in the unit.

[0155] According to another preferred embodiment, the process according to the invention comprises:

[0156] during the protection phase:

[0157] modifying the protected software:

[0158] by choosing, in the source of the protected software, at least one conditional branch carried out in at least one chosen algorithmic processing,

[0159] by modifying at least one chosen portion of the source of the protected software, this modification being such that during the execution of the protected software, the functionality of at least one chosen conditional branch is executed, by means of the second execution part, in the unit,

[0160] and by producing:

[0161] the first object part of the protected software, said first object part being such that during the execution of the protected software, the functionality of at least one chosen conditional branch is executed in the unit,

[0162] and the second object part of the protected software, said second object part being such that, after upload to the unit and during the execution of the protected software, appears the second execution part by means of which the functionality of at least one chosen conditional branch is executed,

[0163] and during the usage phase:

[0164] in the presence of the unit and each time a portion of the first execution part imposes it, executing the functionality of at least one conditional branch in the unit, so that said portion is executed correctly and that, consequently, the protected software is completely functional,

[0165] and in the absence of the unit and in spite of the request by a portion of the first execution part to execute the functionality of a conditional branch in the unit, not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that consequently, the protected software is not completely functional.

[0166] According to a variant embodiment, the process according to the invention comprises, during the protection phase, modifying the protected software:

[0167] by choosing, in the source of the protected software, at least one series of chosen conditional branches,

[0168] by modifying at least one chosen portion of the source of the protected software, this modification being such that during the execution of the protected software, the overall functionality of at least one chosen series of conditional branches is executed, by means of the second execution part, in the unit,

[0169] and by producing:

[0170] the first object part of the protected software, said first object part being such that during the execution of the protected software, the functionality of at least one chosen series of conditional branches is executed in the unit,

[0171] and the second object part of the protected software, said second object part being such that, after upload to the unit and during the execution of the protected software, appears the second execution part by means of which the overall functionality of at least one chosen series of conditional branches is executed.

[0172] The process according to the invention thus enables to protect usage of a software by using a processing and memorizing unit which presents the characteristic of containing a part of the software being executed. It follows that any derived version of the software attempting to work without the processing and memorizing unit imposes to recreate the part of the software contained in the processing and memorizing unit during the execution, or else said derived version of the software will not be completely functional.

BRIEF DESCRIPTION OF THE DRAWINGS

[0173] Various other characteristics emerge from the description made below in reference to the appended diagrams which show, as non-limiting examples, embodiments and implementations of the subject of the invention.

[0174]FIGS. 10 and 11 are functional blocks diagrams illustrating the various representations of a software respectively not protected and protected by the process in accordance with the invention.

[0175] FIGS. 20 to 22 illustrate as examples, various embodiments of an apparatus implementing the process in accordance with the invention.

[0176]FIGS. 30 and 31 are functional blocks diagrams making explicit the general principle of the process in accordance with the invention.

[0177] FIGS. 40 to 43 are diagrams illustrating the protection process according to the invention implementing the principle of protection by variable.

[0178] FIGS. 70 to 74 are diagrams illustrating the protection process according to the invention implementing the principle of protection by detection and coercion.

[0179] FIGS. 80 to 85 are diagrams illustrating the protection process according to the invention implementing the principle of protection by par renaming.

[0180] FIGS. 90 to 92 are diagrams illustrating the protection process according to the invention implementing the principle of protection by conditional branch.

[0181]FIG. 100 is a diagram illustrating the different phases of implementation of the subject of the invention.

[0182]FIG. 110 illustrates an embodiment of a system allowing the implementation of the construction stage of the protection phase in accordance with the invention.

[0183]FIG. 120 illustrates an embodiment of a pre-customization unit used in the protection process in accordance with the invention.

[0184]FIG. 130 illustrates an embodiment of a system allowing the implementation of the tools making stage of the protection phase in accordance with the invention.

[0185]FIG. 140 illustrates an embodiment of a system allowing the implementation of the protection process according to the invention.

[0186]FIG. 150 illustrates an embodiment of a customization unit used in the protection process in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0187] In the rest of the description, the following definitions will be used:

[0188] A data processing system 3 is a system able to execute a program.

[0189] A processing and memorizing unit is a unit able:

[0190] to accept data provided by a data processing system 3,

[0191] to return data to the data processing system 3,

[0192] to store data at least partly in secret and to retain at least a part of said data even if the unit is switched off,

[0193] and to carry out algorithmic processing on said data, part or all of the result being secret.

[0194] A unit 6 is a processing and memorizing unit implementing the process according to the invention.

[0195] A blank unit 60 is a unit which does not implement the process according to the invention, but which can receive data transforming it into a unit 6.

[0196] A pre-customized unit 66 is a blank unit 60 which has received part of data enabling it, after reception of supplementary data, to be transformed into a unit 6.

[0197] The upload of information to a blank unit 60 or a pre-customized unit 66 corresponds to a transfer of information to the blank unit 60 or the pre-customized unit 66, and to a storage of said transferred information. The transfer can possibly include a change of the information format.

[0198] A variable, a function or data contained in the data processing system 3 will be indicated by an uppercase letter, while a variable, a function or data contained in the unit 6 will be indicated by a lowercase letter.

[0199] A “protected software”, is a software which has been protected by at least one of the principles of protection implemented by the process in accordance with the invention.

[0200] A “vulnerable software”, is a software which has not been protected by any principle of protection implemented by the process in accordance with the invention.

[0201] In the case where differentiation between a vulnerable software and a protected software is not important, the term “software” is used.

[0202] A software has various representations depending on the instant considered in its life cycle:

[0203] a source representation,

[0204] an object representation,

[0205] a distribution,

[0206] or a dynamic representation.

[0207] A source representation of a software is understood as a representation which after transformation, results in an object representation. A source representation can offer different levels, from a conceptual abstract level to a level executable directly by a data processing system or a processing and memorizing unit.

[0208] An object representation of a software corresponds to a level of representation which after transfer to a distribution and upload to a data processing system or a processing and memorizing unit, can be executed. It can be, for instance, a binary code, an interpreted code, etc.

[0209] A distribution is a physical or virtual support containing the object representation, said distribution having to be put at the user's disposal to enable them to use the software.

[0210] A dynamic representation corresponds to the execution of the software from its distribution.

[0211] A portion of a software corresponds to some part of the software and can, for instance correspond, to one or several consecutive or not instructions, and/or one or several consecutive or not functional blocks, and/or one or several functions, and/or one or several subprograms, and/or one or several modules. A portion of a software can also correspond to all of said software.

[0212]FIGS. 10 and 11 illustrate the various representations respectively of a vulnerable software 2 v in the general sense, and of a protected software 2 p protected according to the process in accordance with the invention.

[0213]FIG. 10 illustrates various representations of a vulnerable software 2 v appearing during its life cycle. The vulnerable software 2 v can thus appear under any of the following representations:

[0214] a source representation 2 vs,

[0215] an object representation 2 vo,

[0216] a distribution 2 vd. Said distribution can have commonly the form of a physical distribution medium such as a CDROM or the form of files distributed through a network (GSM, Internet, etc.),

[0217] or a dynamic representation 2 ve corresponding to the execution of the vulnerable software 2 v on a data processing system 3 of any known type, which classically includes, at least one processor 4.

[0218]FIG. 11 illustrates various representations of a protected software 2 p appearing during its life cycle. The protected software 2 p can thus appear under any of the following representations:

[0219] a source representation 2 ps including a first source part intended for the data processing system 3 and a second source part intended for the unit 6, part of said source parts can commonly be contained in common files,

[0220] an object representation 2 po including a first object part 2 pos intended for the data processing system 3 and a second object part 2 pou intended for the unit 6,

[0221] a distribution 2 pd including:

[0222] a first distribution part 2 pds containing the first object part 2 pos, said first distribution part 2 pds being intended for the data processing system 3 and which can commonly have the form of a physical distribution medium such as a CDROM or the form of files distributed through a network (GSM, Internet, etc.),

[0223] and a second distribution part 2 pdu having the form:

[0224] of at least one pre-customized unit 66 to which a part of the second object part 2 pou has been uploaded and for which the user has to finish the customization by uploading supplementary data so as to obtain a unit 6, said supplementary data being obtained, for instance, by download through a network,

[0225] or of at least one unit 6 to which the second object part 2 pou has been uploaded,

[0226] or a dynamic representation 2 pe corresponding to the execution of the protected software 2 p. Said dynamic representation 2 pe includes a first execution part 2 pes which is executed in the data processing system 3 and an second execution part 2 peu which is executed in the unit 6.

[0227] In the case where the differentiation between the different representations of the protected software 2 p is not important, the expressions first part of the protected software and second part of the protected software shall be used.

[0228] The implementation of the process according to the invention in accordance with the dynamic representation of FIG. 11, uses an apparatus 1 p including a data processing system 3 linked up by a link 5 to a unit 6. The data processing system 3 is of any type and includes, classically, at least one processor 4. The data processing system 3 can be a computer or be part, for instance, of various machines, devices, fixed or mobile products, or vehicles in the general sense. The link 5 can be realized in any possible way, such as for instance a serial link, a USB bus, a radio link, an optical link, a network link or a direct electric connection to a circuit of data processing system 3, etc. It should be observed that the unit 6 can possibly be physically located inside the same integrated circuit than the processor 4 of the data processing system 3. In this case, the unit 6 can be considered as a co-processor in relation to the processor 4 of the data processing system 3 and the link 5 is internal to the integrated circuit.

[0229] FIGS. 20 to 22 show in an illustrative and non-limiting manner, various embodiments of the apparatus 1 p allowing the implementation of the protection process in accordance with the invention.

[0230] In the embodiment illustrated in FIG. 20, the protection apparatus 1 p includes, as a data processing system 3, a computer and, as a unit 6, a chip card 7 and its interface 8 commonly called card reader. The computer 3 is linked up to the unit 6 by a link 5. During the execution of the protected software 2 p, the first execution part 2 pes which is executed in the computer 3 and the second execution part 2 peu which is executed in the chip card 7 and its interface 8, must both be functional so that the protected software 2 p is completely functional.

[0231] In the embodiment illustrated in FIG. 21, the protection apparatus 1 p equips a product 9 in the general sense, including various components 10 adapted to the function(s) assumed by such a product 9. The protection apparatus 1 p includes, on the one hand, a data processing system 3 embedded in the product 9 and, on the other hand, a unit 6 associated with the product 9. So that the product 9 is completely functional, the protected software 2 p, must be completely functional. Thus, during the execution of the protected software 2 p, the first execution part 2 pes which is executed in the data processing system 3 and the second execution part 2 peu which is executed in the unit 6, must both be functional. Said protected software 2 p enables therefore indirectly, to protect against unauthorized usage, the product 9 or one of its functionalities. For instance, the product 9 can be an installation, a system, a machine, a toy, a piece of domestic appliances, a phone, etc.

[0232] In the embodiment illustrated in FIG. 22, the protection apparatus 1 p includes several computers, as well as part of a communication network. The data processing system 3 is a first computer linked up by a link 5 of network type, to a unit 6 constituted by a second computer. For the implementation of the invention, the second computer 6 is used as a license server for a protected software 2 p. During the execution of the protected software 2 p, the first execution part 2 pes which is executed in the first computer 3 and the second execution part 2 peu which is executed in the second computer 6, must both be functional so that the protected software 2 p is completely functional.

[0233]FIG. 30 enables to make explicit more precisely, the protection process in accordance with the invention. It should be observed that a vulnerable software 2 v, is considered as being executed totally in a data processing system 3. On the other hand, in the case of the implementation of a protected software 2 p, the data processing system 3 includes transfer means 12 linked up by the link 5, to transfer means 13 being part of the unit 6 enabling to establish communication between the first execution part 2 pes and the second execution part 2 peu of the protected software 2 p.

[0234] It must be considered that the transfer means 12, 13 are of software and/or hardware nature and are capable of providing and, possibly, optimizing the data communication between the data processing system 3 and the unit 6. Said transfer means 12, 13 are adapted to enable to have at one's disposal a protected software 2 p which is, preferably, independent from the type of link 5 used. Said transfer means 12, 13 are not part of the subject of the invention and are not described more precisely as they are well known by the Man of art. The first part of the protected software 2 p includes commands. During the execution of the protected software 2 p, the execution of said commands by the first execution part 2 pes enables the communication between the first execution part 2 pes and the second execution part 2 peu. In the rest of the description, said commands are represented by IN, OUT or TRIG.

[0235] As illustrated in FIG. 31, to allow the implementation of the second execution part 2 peu of the protected software 2 p, the unit 6 includes protection means 14. The protection means 14 include memorization means 15 and processing means 16.

[0236] For the sake of simplification in the rest of the description, it is chosen to consider, during the execution of the protected software 2 p, the presence of the unit 6 or the absence of the unit 6. In actual fact, a unit 6 providing protection means 14 not adapted to the execution of the second execution part 2 peu of the protected software 2 p is also considered as missing, each time the execution of the protected software 2 p is not correct. In other words:

[0237] a unit 6 physically present and including protection means 14 adapted to the execution of the second execution part 2 peu of the protected software 2 p, is always considered as present,

[0238] a unit 6 physically present but including protection means 14 not adapted, i.e. not allowing the correct implementation of the second execution part 2 peu of the protected software 2 p is considered as present, when it works correctly, and as missing when it does not work correctly,

[0239] and a unit 6 physically missing is always considered as missing.

[0240] In the case where the unit 6 is constituted by a chip card 7 and its interface 8, the transfer means 13 are split into two parts, one being on the interface 8 and the other one being on the chip card 7. In this embodiment, the absence of the chip card 7 is considered as equivalent to the absence of the unit 6. In other words, in the absence of the chip card 7 and/or its interface 8, the protection means 14 are not accessible and do not enable the execution of the second execution part 2 peu of the protected software 2 p, so much so that the protected software 2 p is not completely functional.

[0241] In accordance with the invention, the protection process aims at implementing a principle of protection, called by << detection and coercion >>, a description of which is carried out in relation to FIGS. 70 to 74.

[0242] For the implementation of the principle of protection by detection and coercion, are defined:

[0243] at least one software execution characteristic liable to be monitored at least in part in the unit 6,

[0244] at least one criterion to abide by for at least one software execution characteristic,

[0245] detection means 17 to implement in the unit 6 and enabling to detect that at least one software execution characteristic does not abide by at least one associated criterion,

[0246] and coercion means 18 to implement in the unit 6 and enabling to inform the data processing system 3 and/or modify the execution of a software, when at least one criterion is not abided by.

[0247] For the implementation of the principle of protection by detection and coercion, are also constructed exploitation means enabling to transform a blank unit 60 into a unit 6 implementing at least the detection means 17 and the coercion means 18.

[0248]FIG. 70 illustrates the means necessary to the implementation of this principle of protection by detection and coercion. The unit 6 includes the detection means 17 and the coercion means 18 belonging to the processing means 16. The coercion means 18 are informed by the detection means 17 that a criterion has not been abided by.

[0249] More precisely, the detection means 17 use information coming from the transfer means 13 and/or from the memorization means 15 and/or from the processing means 16, so as to monitor one or several software execution characteristics. For each software execution characteristic is set at least one criterion to abide by.

[0250] In the case where it is detected that at least one software execution characteristic does not abide by at least one criterion, the detection means 17 inform the coercion means 18 of it. Said coercion means 18 are adapted to modify, in the appropriate way, the state of the unit 6.

[0251] For the implementation of the principle of protection by detection and coercion, are also chosen:

[0252] at least one software execution characteristic to monitor, among the software execution characteristics liable to be monitored,

[0253] at least one criterion to abide by for at least one chosen software execution characteristic,

[0254] in the source of the vulnerable software 2 vs, at least one algorithmic processing for which at least one software execution characteristic is to be monitored,

[0255] and in the source of the vulnerable software 2 vs, at least one portion containing at least one chosen algorithmic processing.

[0256] At least one chosen portion of the source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps. This modification is such that, during the execution of the protected software 2 p, among others:

[0257] at least one portion of the first execution part 2 pes, which is executed in the data processing system 3, takes into account that at least one chosen software execution characteristic is to be monitored, at least in part in the unit 6,

[0258] and the second execution part 2 peu, which is executed in the unit 6, monitors at least in part, a chosen software execution characteristic.

[0259] During the execution of the protected software 2 p, protected by this principle of protection by detection and coercion, in the presence of the unit 6:

[0260] as long as all the criteria corresponding to all the monitored execution characteristics of all the modified portions of the protected software 2 p are abided by, said modified portions of the protected software 2 p work nominally, so that said protected software 2 p works nominally,

[0261] and if at least one of the criteria corresponding to a monitored execution characteristic of a portion of the protected software 2 p is not abided by, the data processing system 3 is informed of it and/or the functioning of the portion of the protected software 2 p is modified, so that the functioning of the protected software 2 p is modified.

[0262] Naturally, in the absence of the unit 6, at least one request by a portion of the first execution part 2 pes of the protected software 2 p to use the unit 6 cannot be fulfilled correctly so that at least said portion is not executed correctly and that consequently the protected software 2 p is not completely functional.

[0263] For the implementation of the principle of protection by detection and coercion, two types of software execution characteristics are used preferentially.

[0264] The first type of software execution characteristic corresponds to a variable of measurement of the execution of a software and the second type corresponds to a profile of usage of a software. Said two types of characteristics can be used independently or in combination.

[0265] For the implementation of the principle of protection by detection and coercion using, as execution characteristic, a variable of measurement of software execution, are defined:

[0266] in the memorization means 15, the possibility to memorize at least one variable of measurement used to quantify the usage of at least one functionality of a software,

[0267] in the detection means 17, the possibility to monitor at least one threshold associated to each variable of measurement,

[0268] and actualization means enabling to update each variable of measurement depending on the usage of the functionality to which it is associated.

[0269] Are also constructed exploitation means implementing, in addition to the detection means 17 and the coercion means 18, the actualization means.

[0270] Are also chosen, in the source of the vulnerable software 2 vs:

[0271] at least one functionality of the vulnerable software 2 v whose usage is liable to be monitored using a variable of measurement,

[0272] at least one variable of measurement used to quantify the usage of said functionality,

[0273] at least one threshold associated to the variable of measurement corresponding to a limit of usage of said functionality,

[0274] and at least one method of update of the variable of measurement depending on the usage of said functionality.

[0275] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the second execution 2 peu:

[0276] actualizes the variable of measurement depending on the usage of said functionality,

[0277] and takes into account at least one threshold crossing.

[0278] In other words, during the execution of the protected software 2 p, the variable of measurement is updated depending on the usage of said functionality, and when the threshold is crossed, the detection means 17 inform of it the coercion means 18 which make an adapted decision to inform the data processing system 3 and/or to modify the processings carried out by the processing means 16 enabling to modify the functioning of the portion of the protected software 2 p, so that the functioning of the protected software 2 p is modified.

[0279] For the implementation of a first preferred variant embodiment of the principle of protection by detection and coercion using, as characteristic, a variable of measurement, are defined:

[0280] for at least one variable of measurement, several associated thresholds,

[0281] and different coercion means corresponding to each of said thresholds.

[0282] Are also chosen, in the source of the vulnerable software 2 vs:

[0283] at least one variable of measurement used to quantify the usage of at least one functionality of the software and to which must be associated several thresholds corresponding to different limits of usage of said functionalities,

[0284] and at least two thresholds associated to the variable of measurement.

[0285] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the second execution part 2 peu:

[0286] actualizes the variable of measurement depending on the usage of said functionality,

[0287] and takes into account, differently, the crossing of the various thresholds.

[0288] In other words, classically, during the execution of the protected software 2 p, when the first threshold is crossed, the unit 6 informs the data processing system 3 enjoining the protected software 2 p not to use said functionality anymore. If the protected software 2 p carries on using said functionality, the second threshold will potentially be crossed. In the case where the second threshold is crossed, the coercion means 18 can make the chosen functionality ineffective and/or make the protected software 2 p ineffective.

[0289] For the implementation of a second preferred variant embodiment of the principle of protection by detection and coercion using, as characteristic, a variable of measurement, are defined refilling means enabling to credit at least one software functionality monitored by a variable of measurement with at least one additional usage.

[0290] Are also constructed exploitation means implementing, in addition to the detection means 17, the coercion means 18 and the actualization means, the refilling means.

[0291] Is also chosen, in the source of the vulnerable software 2 vs, at least one variable of measurement used to limit the usage of at least one functionality of the software and which must be able to be credited with at least one additional usage.

[0292] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps, this modification being such that, during a phase called of refilling, at least one additional usage of at least one functionality corresponding to a chosen variable of measurement can be credited.

[0293] Is carried out, during the phase of refilling, the reactualization of at least one chosen variable of measurement and/or of at least one associated threshold, so as to allow at least one additional usage of the corresponding functionality. In other words, it is possible, during the phase of refilling, to credit additional usages of at least one functionality of the protected software 2 p.

[0294] For the implementation of the principle of protection by detection and coercion using, as characteristic, a profile of software usage, is defined as criterion to abide by for said profile of usage, at least one feature of software execution.

[0295] Are also chosen, in the source of the vulnerable software 2 vs:

[0296] at least one profile of usage to monitor,

[0297] and at least one feature of execution by which at least one chosen profile of usage must abide.

[0298] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the second execution part 2 peu abides by all the chosen features of execution. In other words, the unit 6 itself monitors the way the second execution part 2 peu is executed and can inform the data processing system 3 and/or modify the functioning of the protected software 2 p, in the case where at least one feature of execution is not abided by.

[0299] During the execution of the protected software 2 p, protected by this principle, in the presence of the unit 6:

[0300] as long as all the features of execution of all the modified portions of the protected software 2 p are abided by, said modified portions of the protected software 2 p work nominally, so that said protected software 2 p works nominally,

[0301] and if at least one feature of execution of a portion of protected software 2 p is not abided by, the data processing system 3 is informed of it and/or the functioning of the portion of the protected software 2 p is modified, so that the functioning of the protected software 2 p is modified.

[0302] The monitoring of different features of execution can be considered, like for instance the monitoring of the presence of instructions including a marker or the monitoring of the execution chaining for at least one part of the instructions.

[0303] For the implementation of the principle of protection by detection and coercion using as feature of execution to abide by, the monitoring of the execution chaining for at least one part of the instructions, are defined:

[0304] a an instructions set, whose instructions are liable to be executed in the unit 6,

[0305] a set of instructions commands for said instructions set, said instructions commands are liable to be executed in the data processing system 3. The execution of each of said instructions commands in the data processing system 3 triggers in the unit 6, the execution of the corresponding instruction,

[0306] detection means 17 enabling to detect that the chaining of the instructions does not correspond to the expected one,

[0307] and coercion means 18 enabling to inform the data processing system 3 and/or to modify the execution of a software when the chaining of the instructions does not correspond to the expected one.

[0308] Are also constructed exploitation means enabling the unit 6 to also execute the instructions of the instructions set, the execution of said instructions being triggered by the execution in the data processing system 3 of the instructions commands.

[0309] Is also chosen, in the source of the vulnerable software 2 vs, at least one algorithmic processing which must be remoted in the unit 6 and for which the chaining of at least one part of the instructions is to be monitored.

[0310] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the vulnerable software 2 ps, this modification being such that, during the execution of the protected software 2 p:

[0311] the second execution part 2 peu executes at least the functionality of the chosen algorithmic processing,

[0312] the chosen algorithmic processing is split into instructions,

[0313] the chaining by which at least some of the instructions must abide during their execution in the unit 6 is specified,

[0314] and the first execution part 2 pes of the protected software 2 p executes instructions commands which trigger the execution of the instructions in the unit 6.

[0315] During the execution of the protected software 2 p, protected by this principle, in the presence of the unit 6:

[0316] as long as the chaining of the instructions of all the modified portions of the protected software 2 p, executed in the unit 6 corresponds to the expected one, said modified portions of the protected software 2 p work nominally, so that said protected software 2 p works nominally,

[0317] and if the chaining of the instructions of a portion of the protected software 2 p executed in the unit 6 does not correspond to the expected one, the data processing system 3 is informed of it and/or the functioning of the portion of protected software 2 p is modified, so that the functioning of the protected software 2 p is modified.

[0318]FIG. 71 illustrates an example of implementation of the principle of protection by detection and coercion using, as feature of execution to abide by the monitoring of the execution chaining of a at least one part of the instructions, in the case where the expected chaining is abided by.

[0319] The first execution part 2 pes of the protected software 2 p, executed in the data processing system 3, executes instructions commands CI_(i) triggering, in the unit 6 the execution of the instructions i_(i) belonging to the instructions set. In said instructions set, at least some of the instructions each include a part defining the functionality of the instruction and a part enabling to verify the expected chaining for the execution of the instructions. In this example, the instructions commands CI_(i) are represented by TRIG(i_(i)) and the expected chaining for the execution of the instructions is i_(n), i_(n+1) and i_(n+2). The execution in the unit 6, of the instruction i_(n) gives the result a and the execution of the instruction i_(n+1) gives the result b. The instruction i_(n+2) uses as operand, the results a and b of the instructions i_(n) and i_(n+i) and its execution gives the result c.

[0320] Taking into account that said chaining of the instructions executed in the unit 6 corresponds to the expected one, it results in a normal or nominal functioning of the protected software 2 p.

[0321]FIG. 72 illustrates an example of implementation of the principle of protection by detection and coercion using, as feature of execution to abide by, the monitoring of the execution chaining of at least one part of the instructions, in the case where the expected chaining is not abided by.

[0322] According to this example, the expected chaining for the execution of the instructions is still i_(n), i_(n+1) and i_(n+2). However, the execution chaining is modified by the replacement of the instruction i_(n) with the instruction i′_(n), so that the chaining actually executed is i′_(n), i_(n+1) and i_(n+2). The execution of the instruction i′_(n) gives the result a, i.e. the same result that the execution of the instruction i_(n). However, at the latest during the execution of the instruction i_(n+2), the detection means 17 detect that the instruction i′_(n) does not correspond to the expected instruction to generate the result a used as operand of the instruction i_(n+2). The detection means 17 inform of it the coercion means 18 which modify accordingly, the functioning of the instruction i_(n+2), so that the execution of the instruction i_(n+2) gives the result c′ which can be different than c. Naturally, if the execution of the instruction i′_(n) gives a result a′ different from the result a of the instruction i_(n), it is clear that the result of the instruction i_(n+2) can also be different from c.

[0323] Inasmuch as the execution chaining of the instructions executed in the unit 6 does not correspond to the expected one, a modification of the functioning of the protected software 2 p can therefore be obtained.

[0324]FIGS. 73 and 74 illustrates a preferred variant embodiment of the principle of protection by detection and coercion using, as feature of execution to abide by, the monitoring of the execution chaining of at least one part of the instructions. According to this preferred variant, is defined an instructions set whose at least some instructions work with registers and use at least one operand with the intention of returning a result.

[0325] As illustrated in FIG. 73, are defined for at least some of the instructions working with registers, a part PF defining the functionality of the instruction and a part PE defining the expected chaining for the execution of the instructions. The part PF corresponds to the operation code known by the Man of art. The part PE defining the expected chaining, includes bits fields corresponding to:

[0326] an identification field of the instruction CII,

[0327] and for each operand k of the instruction, with k varying from 1 to K, and K number of operands of the instruction:

[0328] a flag field CD_(k), indicating whether or not it is appropriate to verify the origin of the operand k,

[0329] and an expected identification field CIP_(k) of the operand, indicating the expected identity of the instruction which has generated the contents of the operand k.

[0330] As illustrated in FIG. 74, the instructions set includes V registers belonging to the processing means 16, each register being named R_(v), with v varying from 1 to V. For each register R_(v), are defined two fields, namely:

[0331] a functional field CF_(v), known by the Man of art and enabling to store the result of the execution of the instructions,

[0332] and a generated identification field CIG_(v) enabling to memorize the identity of the instruction which has generated the contents of the functional field CF_(v). Said generated identification field CIG_(v) is automatically updated with the contents of the identification field of the instruction CII which has generated the functional field CF_(v). Said generated identification field CIG_(v) is neither accessible, nor modifiable by any of the instructions and is solely used for the detection means 17.

[0333] During the execution of an instruction, the detection means 17 carry out for each operand k the following operations:

[0334] the flag field CD_(k) is read,

[0335] if the flag field CD_(k) imposes it, the expected identification field CIP_(k) and the generated identification field CIG_(v) corresponding to the register used by the operand k are both read,

[0336] the equality of the two fields CIP_(k) and CIG_(v) is checked,

[0337] and if the equality is false, the detection means 17 consider that the execution chaining of the instructions is not abided by.

[0338] The coercion means 18 enable to modify the result of the instructions when the detection means 17 has informed them of an instructions chaining not abided by. A preferred embodiment is carried out by modifying the functional part PF of the instruction currently executed or the functional part PF of subsequent instructions.

[0339] According to another advantageous characteristic of the invention, the protection process aims at implementing a principle of protection called by << variable >> a description of which is carried out in relation to FIGS. 40 to 43.

[0340] For the implementation of the principle of protection by variable, is chosen in the source of the vulnerable software 2 vs at least one variable which, during the execution of the vulnerable software 2 v, partially defines its state. By state of a software, must be understood the set of pieces of information, at a given moment, necessary to the complete execution of said software, so much so that the absence of such a chosen variable prejudices the complete execution of said software. Is also chosen at least one portion of the source of the vulnerable software 2 vs containing at least one chosen variable.

[0341] At least one chosen portion of the source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps. This modification is such that during the execution of the protected software 2 p, at least one portion of the first execution part 2 pes which is executed in the data processing system 3, takes into account that at least one chosen variable or at least one copy of chosen variable resides in the unit 6.

[0342]FIG. 40 illustrates an example of execution of a vulnerable software 2 v. In this example, during the execution of the vulnerable software 2 v in the data processing system 3, appear:

[0343] at time instant t₁, the assignment of the data X to the variable V₁, represented by V₁←X,

[0344] at time instant t₂, the assignment of the value of the variable V₁ to the variable Y, represented by Y←V₁,

[0345] and at time instant t₃, the assignment of the value of the variable V₁ to the variable Z, represented by Z←V₁.

[0346]FIG. 41 illustrates an example of a first form of implementation of the invention for which the variable resides in the unit 6. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p, and in presence of the unit 6, appear:

[0347] at time instant t₁, the execution of a transfer command triggering the transfer of the data X from the data processing system 3 to the variable v₁ located in the memorization means 15 of the unit 6, said transfer command being represented by OUT(v₁, X) and corresponding in the end to the assignment of the data X to the variable v₁,

[0348] at time instant t₂, the execution of a transfer command triggering the transfer of the value of the variable v₁ residing in the unit 6 to the data processing system 3 so as to assign it to the variable Y, said transfer command being represented by IN(v₁) and corresponding in the end to the assignment of the value of the variable v₁ to the variable Y,

[0349] and at time instant t₃, the execution of a transfer command triggering the transfer of the value of the variable v₁ residing in the unit 6 to the data processing system 3 so as to assign it to the variable Z, said transfer command being represented by IN(v₁) and corresponding in the end to the assignment of the value of the variable v₁ to the variable Z.

[0350] It should be observed that during the execution of the protected software 2 p, at least one variable resides in the unit 6. Thus, when a portion of the first execution part 2 pes of the protected software 2 p imposes it, and in the presence of the unit 6, the value of said variable residing in the unit 6 is transferred to the data processing system 3 to be used by the first execution part 2 pes of the protected software 2 p, so much so that said portion is executed correctly and that, consequently, the protected software 2 p is completely functional.

[0351]FIG. 42 illustrates an example of a second form of implementation of the invention for which a copy of the variable resides in the unit 6. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p, and in the presence of the unit 6, appear:

[0352] at time instant t₁, the assignment of the data X to the variable V₁ located in the data processing system 3, as well as the execution of a transfer command triggering the transfer of the data X from the data processing system 3 to the variable v₁ located in the memorization means 15 of the unit 6, said transfer command being represented by OUT(v₁, X),

[0353] at time instant t₂, the assignment of the value of the variable V₁ to the variable Y,

[0354] and at time instant t₃, the execution of a transfer command triggering the transfer of the value of the variable v₁ residing in the unit 6 to the data processing system 3 so as to affect it to the variable Z, said transfer command being represented by IN(v₁).

[0355] It should be observed that during the execution of the protected software 2 p, at least one copy of a variable resides in the unit 6. Thus, when a portion of the first execution part 2 pes of the protected software 2 p, imposes it, and in the presence of the unit 6, the value of said copy of variable residing in the unit 6 is transferred to the data processing system 3 to be used by the first execution part 2 pes of the protected software 2 p, so much so that said portion is executed correctly and that, consequently, the protected software 2 p is completely functional.

[0356]FIG. 43 illustrates an example of attempt of execution of the protected software 2 p, when the unit 6 is missing. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p:

[0357] at time instant t₁, the execution of the transfer command OUT(v₁, X) cannot trigger the transfer of the data X to the variable v₁, taking into account the absence of the unit 6,

[0358] at time instant t₂, the execution of the transfer command IN(v₁) cannot trigger the transfer of the value of the variable v₁ to the data processing system 3, taking into account the absence of the unit 6,

[0359] and at time instant t₃, the execution of the transfer command IN(v₁) cannot trigger the transfer of the value of the variable v₁ to the data processing system 3, taking into account the absence of the unit 6.

[0360] It therefore appears that in the absence of the unit 6, at least one request by a portion of the first execution part 2 pes to use a variable or a copy of variable residing in the unit 6, cannot be fulfilled correctly, so that at least said portion is not executed correctly and that, consequently, the protected software 2 p is not completely functional.

[0361] It should be observed that the data transfers between the data processing system 3 and the unit 6 illustrated in the previous examples use only simple assignments but that the Man of art will know how to combine them with other operations to obtain complex operations such as for instance OUT(v1, 2 * X+3) or Z←(5 * v1+v2).

[0362] According to another advantageous characteristic of the invention, the protection process aims at implementing a principle of protection, called by << renaming>> a description of which is carried out in relation to FIGS. 80 to 85.

[0363] For the implementation of the principle of protection by renaming, are defined:

[0364] a set of dependent functions, whose dependent functions are liable to be executed, by means of the second execution part 2 peu, in the unit 6, and possibly to transfer data between the data processing system 3 and the unit 6, said set of dependent functions can be finite or infinite,

[0365] a set of triggering commands for said dependent functions, said triggering commands being liable to be executed in the data processing system 3 and to trigger in the unit 6, the execution of corresponding dependent functions,

[0366] for each triggering command, an order corresponding at least in part to the information transmitted by the first execution part 2 pes, to the second execution part 2 peu, so as to trigger the execution of the corresponding dependent function, said order having the form of at least one argument of the triggering command,

[0367] a method of renaming of the orders designed to be used during the modification of the vulnerable software 2 v, such a method enabling to rename the orders so as to obtain triggering commands with renamed orders enabling to conceal the identity of the corresponding dependent functions,

[0368] and restoring means 20 designed to be used in the unit 6 during the usage phase and enabling to restore the initial order, from the renamed order, so as to restore the dependent function to execute.

[0369] For the implementation of the principle of protection by renaming, are also constructed exploitation means enabling to transform a blank unit 60 into a unit 6 implementing at least the restoring means 20.

[0370] For the implementation of the principle of protection by renaming, are also chosen, in the source of the vulnerable software 2 vs:

[0371] at least one algorithmic processing using at least one operand and returning at least one result,

[0372] and at least one portion of the source of the vulnerable software 2 vs, containing at least one chosen algorithmic processing.

[0373] The source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps. This modification is such that, among others:

[0374] during the execution of the protected software 2 p, at least one portion of the first execution part 2 pes, which is executed in the data processing system 3, takes into account that the functionality of at least one chosen algorithmic processing is executed in the unit 6,

[0375] during the execution of the protected software 2 p, the second execution part 2 peu, which is executed in the unit 6, executes at least the functionality of at least one chosen algorithmic processing,

[0376] each chosen algorithmic processing is split so that during the execution of the protected software 2 p, each chosen algorithmic processing is executed, by means of the second execution part 2 peu, using dependent functions. Preferably, each chosen algorithmic processing is split into dependent functions fd_(n) (with n varying from 1 to N), namely:

[0377] possibly one or several dependent functions enabling the placing of one or several operands at the unit 6's disposal,

[0378] dependent functions, some of which use the operand(s) and execute in combination the functionality of the chosen algorithmic processing, using said operand(s),

[0379] and possibly, one or several dependent functions enabling the placing by the unit 6, at the data processing system 3's disposal of the result of the chosen algorithmic processing,

[0380] during the execution of the protected software 2 p, the second execution part 2 peu executes the dependent functions fd_(n),

[0381] during the execution of the protected software 2 p, the dependent functions are triggered by triggering commands with renamed orders,

[0382] and a sequence of the triggering commands is chosen among the set of sequences allowing the execution of the protected software 2 p.

[0383] The first execution part 2 pes of the protected software 2 p, executed in the data processing system 3, executes triggering commands with renamed orders transferring renamed orders to the unit 6, and triggering in the unit 6 the restoring by means of the restoring means 20, of the orders, and then the execution by means of the second execution part 2 peu, of each of the previously defined dependent functions fd_(n).

[0384] In other words, the principle of protection by renaming is carried out by renaming the orders of the triggering commands, so as to obtain triggering commands with renamed orders whose execution in the data processing system 3, triggers in the unit 6, the execution of the dependent functions which would have been triggered by the triggering commands with not-renamed orders, without however the examination of the protected software 2 p enabling to determine the identity of the executed dependent functions.

[0385]FIG. 80 illustrates an example of execution of a vulnerable software 2 v. In this example, appears during the execution of the vulnerable software 2 v in the data processing system 3, at a certain time instant, the calculation of Z←F(X, Y) corresponding to the assignment to a variable Z of the result of an algorithmic processing represented by a function F and using the operands X and Y.

[0386]FIGS. 81 and 82 illustrate an example of implementation of the invention.

[0387]FIG. 81 illustrates the partial implementation of the invention. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p and in the presence of the unit 6, appear:

[0388] at time instants t₁, t₂, the execution of the triggering commands CD₁, CD₂ triggering in the unit 6, the execution by means of the second execution part 2 peu, of the corresponding dependent functions fd₁, fd₂ which provide the transfer of data X, Y from the data processing system 3 to the memorization zones respectively x, y located in the memorization means 15 of the unit 6, said triggering commands CD₁, CD₂ being represented respectively by OUT(x, X), OUT(y, Y),

[0389] at time instants t₃ to t_(N−1), the execution of the triggering commands CD₃ to CD_(N−1), triggering in the unit 6, the execution by means of the second execution part 2 peu, of the corresponding dependent functions fd₃ to fd_(N−1), said triggering commands CD₃ to CD_(N−1) being represented respectively, by TRIG(fd₃) to TRIG(fd_(N−1)). The series of dependent functions fd₃ to fd_(N−1) executed in combination is algorithmically equivalent to the function F. More precisely, the execution of said triggering commands leads to the execution in the unit 6, of the dependent functions fd₃ to fd_(N−1) which use the contents of the memorization zones x, y and return the result in a memorization zone z of the unit 6,

[0390] and at time instant t_(N), the execution of a triggering command CD_(N) triggering in the unit 6, the execution by means of the second execution part 2 peu, of the dependent function fd_(N) providing the transfer of the result of the algorithmic processing contained in the memorization zone z of the unit 6 to the data processing system 3, so as to assign it to the variable Z, said command being represented by IN(z).

[0391] In this example, to completely implement the invention, are chosen as orders, the first argument of the triggering commands OUT and the argument of the triggering commands TRIG and IN. The orders chosen in this way are renamed using the method of renaming of the orders. In this manner, the orders of the triggering commands CD₁ to CD_(N) i.e. x, y, fd₃, fd_(N−1), z are renamed so as to obtain respectively R(x), R(y), R(fd₃) . . . , R(fd_(N−1)), R(z).

[0392]FIG. 82 illustrates the complete implementation of the invention. In this example, during the execution in the data processing system 3, of the first execution part 2 pes of the protected software 2 p, and in the presence of the unit 6, appear:

[0393] at time instants t₁, t₂, the execution of the triggering commands with renamed orders CDCR₁, CDCR₂, transferring to the unit 6, the renamed orders R(x), R(y) as well as the data X, Y triggering in the unit 6 the restoring by means of the restoring means 20, of the renamed orders to restore the orders i.e. the identity of the memorization zones x, y, and then the execution by means of the second execution part 2 peu, of the corresponding dependent functions fd₁, fd₂ which provide the transfer of the data X, Y from the data processing system 3 to the memorization zones respectively x, y located in the memorization means 15 of the unit 6, said triggering commands with renamed orders CDCR₁, CDCR₂ being represented respectively by OUT (R(x), X), OUT (R(y), Y),

[0394] at time instants t₃ to t_(N−1), the execution of the triggering commands with renamed orders CDCR₃ to CDCR_(N−1), transferring to the unit 6, the renamed orders R(fd₃) to R(fd_(N−1)), triggering in the unit 6 the restoring by means of the restoring means 20, of the orders, i.e. fd₃ to fd_(N−1), and then the execution by means of the second execution part 2 peu, of the dependent functions fd₃ to fd_(N−1), said triggering commands with renamed orders CDCR₃ to CDCR_(N−1) being represented respectively by TRIG (R(fd₃)) to TRIG (R(fd_(N−1))),

[0395] and at time instant t_(N), the execution of the triggering command with renamed order CDCR_(N) transferring to the unit 6, the renamed order R(z) triggering in the unit 6 the restoring by means of restoring means 20, of the order i.e. the identity of the memorization zone z, and then the execution by means of the second execution part 2 peu, of the dependent function fd_(N) providing the transfer of the result of the algorithmic processing contained in the memorization zone z of the unit 6 to the data processing system 3, so as to assign it to the variable Z, said triggering command with renamed order CDCR_(N) being represented by IN (R(z)).

[0396] In the illustrated example, the triggering commands with renamed orders 1 to N are executed successively. It should be observed that two improvements can be effected:

[0397] The first improvement concerns the case where several algorithmic processings are remoted to the unit 6 and at least the result of one algorithmic processing is used by another algorithmic processing. In this case, some triggering commands with renamed orders used for the transfer, can possibly be removed.

[0398] The second improvement aims at opting for a pertinent sequence of the triggering commands with renamed orders among the set of sequences allowing the execution of the protected software 2 p. In this respect, it is preferable to choose a sequence of the triggering commands with renamed orders which dissociate temporally the execution of the dependent functions, by intercalating, between them portions of code executed in the data processing system 3 and including or not triggering commands with renamed orders used of the determination of other data. FIGS. 83 and 84 illustrate the principle of such an embodiment.

[0399]FIG. 83 shows an example of execution of a vulnerable software 2 v. In this example, appears, during the execution of the vulnerable software 2 v, in the data processing system 3, the execution of two algorithmic processings leading to the determination of Z and Z′, such as Z←F (X, Y) and Z′←F′ (X′, Y′).

[0400]FIG. 84 illustrates an example of implementation of the process according to the invention for which the two algorithmic proccesings chosen in FIG. 83 are remoted to the unit 6. According to such an example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p and in the presence of the unit 6, appear, as explained above, the execution of the triggering commands with renamed orders CDCR₁ to CDCR_(N) corresponding to the determination of Z and the execution of the triggering commands with renamed orders CDCR′₁ to CDCR′_(M) corresponding to the determination of Z′. As illustrated, the triggering commands with renamed orders CDCR₁ to CDCR_(N) are not executed consecutively, inasmuch as the triggering commands with renamed orders CDCR′₁ to CDCR′_(M) as well as other portions of code are intercalated. In the example, the following sequence is thus carried out: CDCR₁, portion of intercalated code, CDCR′₁, CDCR₂, portion of intercalated code, CDCR′₂, CDCR′₃, portion of intercalated code, CDCR′₄, CDCR₃, CDCR₄, . . . , CDCR_(N), CDCR′_(M).

[0401] It should be observed that, during the execution of a portion of the first execution part 2 pes of the protected software 2 p, the triggering commands with renamed orders executed in the data processing system 3, trigger in the unit 6 the restoring of the identity of the corresponding dependent functions and then their execution. Thus, it appears that in the presence of the unit 6, said portion is executed correctly and that, consequently, the protected software 2 p is completely functional.

[0402]FIG. 85 illustrates an example of an attempt of execution of the protected software 2 p, when the unit 6 is missing. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p, at every time instant, the execution of a triggering command with renamed order can trigger neither the restoring of the order nor the execution of the corresponding dependent function, because of the absence of the unit 6. The value to assign to the variable Z cannot therefore be determined correctly.

[0403] It therefore appears, that in the absence of the unit 6, at least one request by a portion of the first execution part 2 pes of the protected software 2 p, to trigger the restoring of an order and the execution of a dependent function in the unit 6 cannot be fulfilled correctly, so that at least said portion is not executed correctly and that, consequently, the protected software 2 p is not completely functional.

[0404] Thanks to this principle of protection by renaming, the examination in the protected software 2 p of the triggering commands with renamed orders does not enable to determine the identity of the dependent functions which have to be executed in the unit 6. It should be observed that the renaming of the orders is carried out during the modification of the vulnerable 2 v to a protected software 2 p.

[0405] According to a variant of the principle of protection by renaming, is defined for at least one dependent function, a family of dependent functions algorithmically equivalent but triggered by different triggering commands with renamed orders. According to this variant, for at least one algorithmic processing using dependent functions, said algorithmic processing is split into dependent functions which for at least one of them is replaced with a dependent function of the same family instead of keeping several occurrences of the same dependent function. To this end, triggering commands with renamed orders are modified to take into account the replacement of dependent functions with dependent functions of the same family. In other words, two dependent functions of the same family have different orders and consequently different triggering commands with renamed orders and, it is not possible, by examining the protected software 2 p, to discover that the dependent functions called are algorithmically equivalent.

[0406] According to a first preferred embodiment of the variant of the principle of protection by renaming, is defined for at least one dependent function, a family of algorithmically equivalent dependent functions, by concatenating a noise field to the information defining the functional part of the dependent function to execute in the unit 6.

[0407] According to a second preferred embodiment of the variant of the principle of protection by renaming, is defined for at least one dependent function, a family of algorithmically equivalent dependent functions by using identification fields.

[0408] According to a preferred variant embodiment of the principle of protection by renaming, is defined as method of renaming of the orders a ciphering method enabling to cipher the orders to transform them into renamed orders. Remember that the renaming of the orders is carried out during the phase of protection P. For this preferred variant, the restoring means 20 are means implementing a deciphering method enabling to decipher the renamed orders and thus to restore the identity of the dependent functions to execute in the unit 6. Said restoring means are implemented in the unit 6 and can be of software or hardware nature. Said restoring means 20 are appealed to during the usage phase U each time a triggering command with renamed order is executed in the data processing system 3 with the intention of triggering in the unit 6, the execution of a dependent function.

[0409] According to another advantageous characteristic of the invention, the protection process aims at implementing a principle of protection called by << conditional branch>> a description of which is carried out in relation to FIGS. 90 to 92.

[0410] For the implementation of the principle of protection by conditional branch, is chosen in the source of the vulnerable software 2 vs, at least one conditional branch BC. Is also chosen at least one portion of the source of the vulnerable software 2 vs containing at least one chosen conditional branch BC.

[0411] At least one chosen portion of the source of the vulnerable software 2 vs is then modified, so as to obtain the source of the protected software 2 ps. This modification is such that, during the execution of the protected software 2 p, among others:

[0412] at least one portion of the first execution part 2 pes, which is executed in the data processing system 3, takes into account that the functionality of at least one chosen conditional branch BC is executed in the unit 6,

[0413] and the second execution part 2 peu, which is executed in the unit 6, executes at least the functionality of at least one chosen conditional branch BC and puts at the data processing system 3's disposal, a piece of information enabling the first execution part 2 pes, to carry on its execution at the chosen spot.

[0414] The first execution part 2 pes of the protected software 2 p, executed in the data processing system 3, executes conditional branches commands, triggering in the unit 6, the execution by means of the second execution part 2 peu, of remoted conditional branches be whose functionality is equivalent to the functionality of the chosen conditional branches BC.

[0415]FIG. 90 illustrates an example of execution of a vulnerable software 2 v. In this example, appears, during the execution of the vulnerable software 2 v in the data processing system 3 at a certain time instant, a conditional branch BC indicating to the vulnerable software 2 v the spot where to carry on its execution, i.e. one of the three possible spots B₁, B₂ or B₃. It must be understood that the conditional branch BC takes the decision to carry on the execution of the software at spot B₁, B₂ or B₃.

[0416]FIG. 91 illustrates an example of implementation of the invention for which the conditional branch chosen to be remoted to the unit 6, corresponds to the conditional branch BC. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p and in the presence of the unit 6, appear:

[0417] at time instant t₁, the execution of the conditional branch command CBC₁ triggering in the unit 6, the execution by means of the second execution part 2 peu, of the remoted conditional branch be algorithmically equivalent to the conditional branch BC, said conditional branch command CBC₁ being represented by TRIG(bc),

[0418] and at time instant t₂, the transfer from the unit 6 to the data processing system 3, of the information enabling the first execution part 2 pes, to carry on its execution at the chosen spot, i.e. the spot B₁, B₂ or B₃.

[0419] It should be observed that during the execution of a portion of the first execution part 2 pes of the protected software 2 p, the conditional branches commands executed in the data processing system 3 trigger the execution of the corresponding remoted conditional branches in the unit 6. Thus, it appears, that in the presence of the unit 6, said portion is executed correctly and that, consequently, the protected software 2 p is completely functional.

[0420]FIG. 92 illustrates an example of an attempt of execution of the protected software 2 p, when the unit 6 is missing. In this example, during the execution in the data processing system 3 of the first execution part 2 pes of the protected software 2 p:

[0421] at time instant t₁, the execution of the conditional branch command CBC₁, cannot trigger the execution of the remoted conditional branch bc, taking into account the absence of the unit 6,

[0422] and at time instant t₂, the transfer of the piece of information enabling the first execution part 2 pes to carry on at the chosen spot fails taking into account the absence of the unit 6.

[0423] It therefore appears that in the absence of the unit 6, at least one request by a portion of the first execution part 2 pes to trigger the execution of a remoted conditional branch in the unit 6, cannot be fulfilled correctly, so that at least said portion is not executed correctly and that, consequently, the protected software 2 p is not completely functional.

[0424] In the previous description in relation to FIGS. 90 to 92, the subject of the invention aims at remoting in the unit 6, a conditional branch. Naturally, a preferred embodiment of the invention can be carried out by remoting in the unit 6, a series of conditional branches whose overall functionality is equivalent to all the functionalities of the conditional branches which have been remoted. The execution of the overall functionality of said series of remoted conditional branches leads to the placing at the data processing system 3's disposal of a piece of information enabling the first execution part 2 pes of the protected software 2 p to carry on its execution at the chosen spot.

[0425] In the previous description in relation to FIGS. 40 to 92, four different principles of software protection have been made explicit generally speaking independently of one another. The protection process in accordance with the invention, is implemented by using the principle of protection by detection and coercion, possibly combined with one or several other principles of protection. In the case where the principle of protection by detection and coercion is complemented by the implementation of at least another principle of protection, the principle of protection by detection and coercion is advantageously complemented by the principle of protection by variable and/or the principle of protection by renaming and/or the principle of protection by conditional branch.

[0426] And when the principle of protection by renaming is also implemented, it can be complemented in its turn by the principle of protection by conditional branch.

[0427] According to the preferred variant embodiment, the principle of protection by detection and coercion is complemented by the principle of protection by variable and by the principle of protection by renaming, complemented by the principle of protection by conditional branch.

[0428] In the case where a principle of protection is applied, in complement to the principle of protection by detection and coercion, its previously carried out description must include, to take into account its combined implementation, the following modifications:

[0429] the notion of vulnerable software must be understood as software vulnerable towards the principle of protection being described. Thus, in the case where a principle of protection has already been applied to the vulnerable software, the expression “vulnerable software” must be interpreted by the reader as the expression “software protected by the principle(s) of protection already applied”;

[0430] the notion of protected software must be understood as software protected towards the principle of protection being described. Thus, in the case where a principle of protection has already been applied, the expression “protected software” must be interpreted by the reader as the expression “new version of the protected software”;

[0431] and the choice(s) made for the implementation of the principle of protection being described must take into account the choice(s) made for the implementation of the principle(s) of protection already applied.

[0432] The rest of the description enables to have a better understanding of the implementation of the protection process in accordance with the invention. This protection process according to the invention is composed, as shown more precisely in FIG. 100:

[0433] first, of a protection phase P during which a vulnerable software 2 v is modified to become a protected software 2 p,

[0434] then, of a usage phase U during which the protected software 2 p is used.

[0435] During this usage phase U:

[0436] in the presence of the unit 6 and each time a portion of the first execution part 2 pes executed in the data processing system 3 imposes it, an imposed functionality is executed in the unit 6, so that said portion is executed correctly and that, consequently, the protected software 2 p is completely functional,

[0437] in the absence of the unit 6 and in spite of the request by a portion of the first execution part 2 pes to execute a functionality in the unit 6, said request cannot be fulfilled correctly, so that at least said portion is not executed correctly and that consequently, the protected software 2 p is not completely functional,

[0438] and possibly of a phase of refilling R during which is credited at least one additional usage of a functionality protected by the implementation of the second preferred variant embodiment of the principle of protection by detection and coercion using as characteristic, a variable of measurement.

[0439] The protection phase P can be split into two protection sub-phases P₁ and P₂. The first one, called prior protection sub-phase P₁, takes place independently of the vulnerable software 2 v to protect. The second one, called subsequent protection sub-phase P₂ is dependent of the vulnerable software 2 v to protect. It should be observed that the prior protection sub-phase P₁ and the subsequent protection sub-phase P₂ can be carried out advantageously by two different persons or two different teams. For instance, the prior protection sub-phase P₁ can be carried out by a person or a company providing the development of software protection systems, while the subsequent protection sub-phase P₂ can be carried out by a person or a company providing the development of software requiring to be protected. Naturally, it is clear that the prior protection sub-phase P₁ and the subsequent protection sub-phase P₂ can also be carried out by the same person or team.

[0440] The prior protection sub-phase P₁ is composed of several stages S₁₁, . . . , S_(1i) for each of which various tasks or jobs are to be carried out.

[0441] The first stage of this prior protection sub-phase P₁ is called “definitions stage S₁₁”. During this definitions stage S₁₁:

[0442] are chosen:

[0443] the type of the unit 6. As an illustrative example, can be chosen as unit 6, a chip card reader 8 and the chip card 7 associated to the reader,

[0444] and the transfer means 12, 13 designed to be implemented respectively in the data processing system 3 and in the unit 6, during the usage phase U and capable of providing the transfer of data between the data processing system 3 and the unit 6,

[0445] are defined:

[0446] at least one software execution characteristic, liable to be monitored at least in part in a unit 6,

[0447] at least one criterion to abide by for at least one software execution characteristic,

[0448] detection means 17 to implement in a unit 6 and enabling to detect that at least one software execution characteristic does not abide by at least one associated criterion,

[0449] and coercion means 18 to implement in a unit 6 and enabling to inform the data processing system 3 and/or modify the execution of a software when at least one criterion is not abided by,

[0450] and in the case where the protection process according to the invention implements the principle of protection by detection and coercion using as characteristic a variable of measurement of the software execution, are also defined:

[0451] as software execution characteristic liable to be monitored, a variable of measurement of the usage of a functionality of a software,

[0452] as criterion to abide by, at least one threshold associated to each variable of measurement,

[0453] and actualization means enabling to update at least one variable of measurement,

[0454] and in the case where the protection process according to the invention also implements a first preferred variant embodiment of the principle of protection by detection and coercion using as characteristic a variable of measurement of the software execution, are also defined:

[0455] for at least one variable of measurement, several associated thresholds,

[0456] and different coercion means corresponding to each of said thresholds,

[0457] and in the case where the protection process according to the invention implements a second preferred variant embodiment of the principle of protection by detection and coercion using as characteristic a variable of measurement of the software execution, are also defined refilling means enabling to add at least one additional usage to at least one software functionality monitored by a variable of measurement,

[0458] and in the case where the protection process according to the invention implements the principle of protection by detection and coercion using as characteristic a profile of software usage, are also defined:

[0459] as software execution characteristic liable to be monitored, a profile of software usage,

[0460] and as criterion to abide by, at least one feature of software execution,

[0461] and in the case where the protection process according to the invention implements the principle of protection by detection and coercion using as feature of execution to abide by, the monitoring of the execution chaining, are also defined:

[0462] an instructions set whose instructions are liable to be executed in the unit 6,

[0463] a set of instructions commands for said instructions set, said instructions commands being liable to be executed in the data processing system 3 and to trigger in the unit 6 the execution of the instructions,

[0464] as profile of usage, the chaining of the instructions,

[0465] as feature of execution, an expected chaining for the execution of the instructions,

[0466] as detection means 17, means enabling to detect that the chaining of the instructions does not correspond to the expected one,

[0467] and as coercion means 18, means enabling to inform the data processing system 3 and/or to modify the functioning of the portion of protected software 2 p when the chaining of the instructions does not correspond to the expected one,

[0468] and in the case where the protection process according to the invention implements a preferred variant embodiment of the principle of protection by detection and coercion using as feature of execution to abide by, the monitoring of the execution chaining, are also defined:

[0469] as instructions set, an instructions set whose at least some instructions work with registers and use at least one operand with the intention of returning a result,

[0470] for at least some of the instructions working with registers:

[0471] a part PF defining the functionality of the instruction,

[0472] and a part defining the expected chaining for the execution of the instructions and including bits fields corresponding to:

[0473] an identification field of the instruction CII,

[0474] and for each operand of the instruction:

[0475] a flag field CD_(k),

[0476] and an expected identification field CIP_(k) of the operand,

[0477] for each register belonging to the exploitation means and used by the instructions set, a generated identification field CIG_(v) in which is automatically memorized the identification of the last instruction which has returned its result in said register,

[0478] as detection means 17, means enabling, during the execution of an instruction, for each operand, when the flag field CD_(k) imposes it, to check the equality of the generated identification field CIG_(v) corresponding to the register used by said operand, and the expected identification field CIP_(k) of the origin of said operand,

[0479] and as coercion means 18, means enabling to modify the result of the instructions, if at least one of the checked equalities is false.

[0480] and in the case where the protection process according to the invention implements the principle of protection by renaming, are also defined:

[0481] as a triggering command, an instruction command,

[0482] as a dependent function, an instruction,

[0483] as an order, at least one argument for a triggering command, corresponding at least in part to the information transmitted by the data processing system 3 to the unit 6, so as to trigger the execution of the corresponding dependent function,

[0484] a method of renaming of the orders enabling to rename the orders so as to obtain triggering commands with renamed orders,

[0485] and restoring means 20 designed to be used in the unit 6 during the usage phase U, and enabling to restore the dependent function to execute, from the renamed order,

[0486] and in the case where the protection process according to the invention implements a variant of the principle of protection by renaming, is also defined for at least one dependent function, a family of dependent functions algorithmically equivalent, but triggered by triggering commands whose renamed orders are different,

[0487] and in the case where the protection process according to the invention implements one of the preferred embodiments of the variant of the principle of protection by renaming, are also defined for at least one dependent function, a family of algorithmically equivalent dependent functions:

[0488] by concatenating a field of noise to the information defining the functional part of the dependent function to execute in the unit 6,

[0489] or by using the identification field of the instruction CII and the expected identification fields CIP_(k) of the operands.

[0490] and in the case where the protection process according to the invention implements a preferred variant of the principle of protection by renaming, are also defined:

[0491] as method of renaming of the orders, a ciphering method to cipher the orders,

[0492] and as restoring means 20, means implementing a deciphering method to decipher the renamed orders and thus restore the identity of the dependent functions to execute in the unit 6.

[0493] During the prior protection sub-phase P₁, the definitions stage S₁₁ is followed by a stage called “construction stage S₁₂”. During such a stage S₁₂, are constructed the transfer means 12, 13 and the exploitation means corresponding to the definitions of the definitions stage S₁₁.

[0494] During this construction stage S₁₂, are therefore carried out:

[0495] the construction of the transfer means 12, 13 enabling, during the usage phase U, the transfer of data between the data processing system 3 and the unit 6,

[0496] the construction:

[0497] of the exploitation means enabling the unit 6, during the usage phase U to also implement the detection means 17 and the coercion means 18,

[0498] and possibly of the exploitation means enabling the unit 6, during the usage phase U to also implement the actualization means,

[0499] and possibly of the exploitation means enabling the unit 6, during the usage phase U to also implement the refilling means,

[0500] and possibly of the exploitation means also enabling the unit 6, during the usage phase U to execute the instructions of the instructions set,

[0501] and when the principle of protection by renaming is also implemented, the construction of the exploitation means enabling the unit 6, during the usage phase U to also implement the restoring means.

[0502] The construction of the exploitation means is carried out classically, through a program development unit and taking into account the definitions intervened in the definitions stages S₁₁. Such a unit is described in the rest of the description in FIG. 110.

[0503] During the prior protection sub-phase P₁, the construction stage S₁₂ can be followed by a stage called “pre-customization stage S₁₃”. During this pre-customization stage S₁₃, at least a part of the transfer means 13 and/or the exploitation means are uploaded to at least one blank unit 60, with the intention of obtaining at least one pre-customized unit 66. It should be observed that part of the exploitation means, once transferred to a pre-customized unit 66, is no longer directly accessible outside said pre-customized unit 66. The transfer of the exploitation means to a blank unit 60 can be carried out through an adapted pre-customization unit, which is described in the rest of the description in FIG. 120. In the case of a pre-customized unit 66, constituted by a chip card 7 and its reader 8, the pre-customization concerns only the chip card 7.

[0504] During the prior protection sub-phase P₁, after the definitions stage S₁₁ and, possibly after the construction stage S₁₂, a stage called “tools making stage S₁₄” can take place. During this tools making stage S₁₄ are made tools enabling to help generate protected software or automate the protection of software. Such tools enable:

[0505] to help choose or to choose automatically in the vulnerable software 2 v to protect:

[0506] the execution characteristic(s) to monitor and, possibly, the algorithmic processing(s) liable to be split into instructions remotable in the unit 6,

[0507] the portion(s) liable to be modified,

[0508] and when the principle of protection by variable is also implemented, the variable(s) liable to be remoted in the unit 6,

[0509] and when the principle of protection by renaming is also implemented, the algorithmic processing(s) liable to be split into dependent functions remotable in the unit 6 and for which the orders of the triggering commands can be renamed,

[0510] and when the principle of protection by conditional branch is also implemented, the conditional branch(es) whose functionality is liable to be remoted in the unit 6,

[0511] and, possibly, to help generate protected software or to automate the protection of software.

[0512] These different tools can be carried out independently or in combination and each tool can have various forms, such as for instance pre-processor, assembler, compiler, etc.

[0513] The prior protection sub-phase P₁ is followed by a subsequent protection sub-phase P₂ which depends on the vulnerable software 2 v to protect. This subsequent protection sub-phase P₂ is composed of several stages as well. The first stage corresponding to the implementation of the principle of protection by detection and coercion is called “creation stage S₂₁”. During this creation stage S₂₁, the choices made during the definition stage S₁₁ are used. With the aid of said choices and possibly of tools constructed during the tools making stage S₁₄, the protected software 2 p is created:

[0514] by choosing at least one software execution characteristic to monitor, among the software execution characteristics liable to be monitored,

[0515] by choosing at least one criterion to abide by for at least one chosen software execution characteristic,

[0516] by choosing, at least one algorithmic processing which, during the execution of the vulnerable software 2 v, uses at least one operand and enables to obtain at least one result, and for which at least one chosen software execution characteristic, is to be monitored,

[0517] by choosing at least one portion of the source of the vulnerable software 2 vs containing, at least one chosen algorithmic processing,

[0518] by producing the source of the protected software 2 ps from the source of the vulnerable software 2 vs, by modifying at least one chosen portion of the source of the vulnerable software 2 vs to obtain at least one modified portion of the source of the protected software 2 ps, this modification being such that:

[0519] during the execution of the protected software 2 p a first execution part 2 pes is executed in the data processing system 3 and a second execution part 2 peu is executed in a unit 6, obtained from the blank unit 60 after upload of information,

[0520] the second execution part 2 peu executes at least the functionality of at least one chosen algorithmic processing,

[0521] and during the execution of the protected software 2 p, at least one chosen execution characteristic is monitored by means of the second execution part 2 peu and the fact that a criterion is not abided by leads to a modification of the execution of the protected software 2 p,

[0522] and by producing:

[0523] a first object part 2 pos of the protected software 2 p, from the source of the protected software 2 ps, said first object part 2 pos being such that during the execution of the protected software 2 p, appears a first execution part 2 pes which is executed in the data processing system 3 and whose at least a portion takes into account that at least one chosen software execution characteristic is monitored,

[0524] and a second object part 2 pou of the protected software 2 p, containing the exploitation means implementing the detection means 17 and the coercion means 18, said second object part 2 pou being such that, after upload to the blank unit 60 and during the execution of the protected software 2 p, appears the second execution part 2 peu by means of which at least one chosen software execution characteristic is monitored and by means of which the fact that a criterion is not abided by leads to a modification of the execution of the protected software 2 p.

[0525] Naturally, the principle of protection by detection and coercion according to the invention can be applied directly during the development of a new software without requiring the prior realization of a vulnerable software 2 v. In this way, a protected software 2 p is obtained directly.

[0526] For the implementation of the principle of protection by detection and coercion using as characteristic a variable of measurement of the software execution, the protected software 2 p is modified:

[0527] by choosing as software execution characteristic to monitor, at least one variable of measurement of the usage of at least one functionality of a software,

[0528] by choosing:

[0529] at least one functionality of the protected software 2 p whose usage is liable to be monitored using a variable of measurement,

[0530] at least one variable of measurement used to quantify the usage of said functionality,

[0531] at least one threshold associated to a chosen variable of measurement corresponding to a limit of usage of said functionality,

[0532] and at least one method of update of a chosen variable of measurement depending on the usage of said functionality,

[0533] and by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the variable of measurement is actualized by means of the second execution part 2 peu depending on the usage of said functionality, and at least one threshold crossing is taken into account.

[0534] For the implementation of a first preferred variant embodiment of the principle of protection by detection and coercion using, as characteristic, a variable of measurement, the protected software 2 p is modified:

[0535] by choosing in the source of the protected software 2 ps, at least one chosen variable of measurement to which must be associated several thresholds corresponding to different limits of usage of the functionality,

[0536] by choosing at least two thresholds associated to the chosen variable of measurement,

[0537] and by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the crossings of the various thresholds are taken into account differently, by means of the second execution part 2 peu.

[0538] For the implementation of a second preferred variant embodiment of the principle of protection by detection and coercion using as characteristic, a variable of measurement, the protected software 2 p is modified:

[0539] by choosing in the source of the protected software 2 ps, at least one chosen variable of measurement enabling to limit the usage of a functionality and which must be able to be credited with at least one additional usage,

[0540] and by modifying at least one chosen portion, this modification being such that during a phase called of refilling, at least one additional usage of at least one functionality corresponding to a chosen variable of measurement can be credited.

[0541] For the implementation of the principle of protection by detection and coercion using as characteristic, a profile of software usage, the protected software 2 p is modified:

[0542] by choosing as software execution characteristic to monitor at least one profile of software usage,

[0543] by choosing at least one feature of execution by which at least one chosen profile of usage must abide,

[0544] and by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that, during the execution of the protected software 2 p, the second execution part 2 peu abides by all the chosen features of execution.

[0545] For the implementation of the principle of protection by detection and coercion using as feature of execution to abide by, the monitoring of the execution chaining, the protected software 2 p is modified:

[0546] by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that:

[0547] at least one chosen algorithmic processing is split so that during the execution of the protected software 2 p, said algorithmic processing is executed by means of the second execution part 2 peu, using instructions,

[0548] for at least one chosen algorithmic processing, instructions commands are integrated to the source of the protected software 2 ps, so that during the execution of the protected software 2 p, each instruction command is executed by the first execution part 2 pes and triggers in the unit 6, the execution by means of the second execution part 2 peu, of an instruction,

[0549] a sequence of the instructions commands is chosen among the set of sequences allowing the execution of the protected software 2 p,

[0550] and the chaining by which must abide at least some of the instructions during their execution in the unit 6 is specified.

[0551] During the subsequent protection sub-phase P₂, and when at least another principle of protection is applied in addition to the principle of protection by detection and coercion, a “modification stage S₂₂” takes place. During this modification stage S₂₂, are used the definitions intervened in the definitions stage S₁₁. Using said definitions and possibly tools constructed during the tools making stage S₁₄, the protected software 2 p is modified to allow the implementation of the principles of protection according to one of the arrangements herebefore defined.

[0552] When the principle of protection by variable is implemented, the protected software 2 p is modified:

[0553] by choosing at least one variable used in at least one chosen algorithmic processing, which during the execution of the protected software 2 p, partially defines the state of the protected software 2 p,

[0554] by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that during the execution of the protected software 2 p, at least one chosen variable or at least one copy of chosen variable resides in the unit 6,

[0555] and by producing:

[0556] the first object part 2 pos of the protected software 2 p, said first object part 2 pos being such that during the execution of the protected software 2 p, at least one portion of the first execution part 2 pes takes also into account that at least one variable or at least one copy of variable resides in the unit 6,

[0557] and the second object part 2 pou of the protected software 2 p, said second object part 2 pou being such that, after upload to the unit 6 and during the execution of the protected software 2 p, appears the second execution part 2 peu by means of which at least one chosen variable, or at least one copy of chosen variable resides too in the unit 6.

[0558] When the principle of protection by renaming is implemented, the protected software 2 p is modified:

[0559] by choosing in the source of the protected software 2 ps, triggering commands,

[0560] by modifying at least one chosen portion of the source of the protected software 2 ps by renaming the orders of the chosen triggering commands, so as to conceal the identity of the corresponding dependent functions,

[0561] and by producing:

[0562] the first object part 2 pos of the protected software 2 p, said first object part 2 pos being such that during the execution of the protected software 2 p, the triggering commands with renamed orders are executed,

[0563] and the second object part 2 pou of the protected software 2 p containing the exploitation means also implementing the restoring means 20, said second object part 2 pou being such that, after upload to the unit 6 and during the execution of the protected software 2 p, the identity of the dependent functions whose execution is triggered by the first execution part 2 pes is restored by means of the second execution part 2 peu, and the dependent functions are executed by means of the second execution part 2 peu.

[0564] For the implementation of a variant of the principle of protection by renaming, the protected software 2 p is modified:

[0565] by choosing, in the source of the protected software 2 ps at least one triggering command with renamed order,

[0566] and by modifying at least one chosen portion of the source of the protected software 2 ps by replacing at least the renamed order of one chosen triggering command with renamed order, with another renamed order, triggering a dependent function of the same family.

[0567] When the principle of protection by conditional branch is implemented, the protected software 2 p is modified:

[0568] by choosing, in the source of the protected software 2 ps, at least one conditional branch carried out in at least one chosen algorithmic processing,

[0569] by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that during the execution of the protected software 2 p, the functionality of at least one chosen conditional branch is executed, by means of the second execution part 2 peu, in the unit 6,

[0570] and by producing:

[0571] the first object part 2 pos of the protected software 2 p, said first object part 2 pos being such that during the execution of the protected software 2 p, the functionality of at least one chosen conditional branch is executed in the unit 6,

[0572] and the second object part 2 pou of the protected software 2 p, said second object part 2 pou being such that, after upload to the unit 6 and during the execution of the protected software 2 p, appears the second execution part 2 peu by means of which the functionality of at least one chosen conditional branch is executed.

[0573] For the implementation of a preferred embodiment of the principle of protection by conditional branch, the protected software 2 p is modified:

[0574] by choosing, in the source of the protected software 2 ps, at least one series of chosen conditional branches,

[0575] by modifying at least one chosen portion of the source of the protected software 2 ps, this modification being such that during the execution of the protected software 2 p, the overall functionality of at least one chosen series of conditional branches is executed, by means of the second execution part 2 peu, in the unit 6,

[0576] and by producing:

[0577] the first object part 2 pos of the protected software 2 p, said first object part 2 pos being such that during the execution of the protected software 2 p, the functionality of at least one chosen series of conditional branches is executed in the unit 6,

[0578] and the second object part 2 pou of the protected software 2 p, said second object part 2 pou being such that, after upload to the unit 6 and during the execution of the protected software 2 p, appears the second execution part 2 peu by means of which the overall functionality of at least one chosen series of conditional branches is executed.

[0579] Naturally, the principles of protection according to the invention can be applied directly during the development of a new software without requiring the prior carrying out of intermediate protected pieces of software. In this way, the creation stage S₂₁ and the modification stage S₂₂ can be carried out concomitantly so as to obtain directly the protected software 2 p.

[0580] During the subsequent protection sub-phase P₂, after the creation stage S₂₁ of the protected software 2 p, and possibly after the modification stage S₂₂, a stage called “customization stage S₂₃” takes place. During this customization stage S₂₃, the second object part 2 pou containing the exploitation means is uploaded to at least one blank unit 60, with the intention of obtaining at least one unit 6, or a part of the second object part 2 pou possibly containing the exploitation means is uploaded to at least one pre-customized unit 66, with the intention of obtaining at least one unit 6. The uploading of this customization information enables to make operational at least one unit 6. It should be observed that part of said information, once transferred to a unit 6, is not directly accessible outside said unit 6. The transfer of the customization information to a blank unit 60 or a pre-customized unit 66 can be carried out through an adapted customization unit which is described in the rest of the description in FIG. 150. In the case of a unit 6, constituted by a chip card 7 and its reader 8, the customization concerns only the chip card 7.

[0581] For the implementation of the protection phase P, various technical means are described more precisely in relation to FIGS. 110, 120, 130, 140 and 150.

[0582]FIG. 110 illustrates an embodiment of a system 25 enabling to implement the construction stage S₁₂ which takes into account the definitions intervened during the definitions stage S₁₁ and during which are constructed the transfer means 12, 13 and possibly, the exploitation means intended for the unit 6. Such a system 25 includes a program development unit or workstation which has classically the form of a computer comprising a system unit, a screen, peripherals such as keyboard-mouse, and including, among others, the following programs: file editors, assemblers, pre-processors, compilers, interpreters, debuggers and link editors.

[0583]FIG. 120 illustrates an embodiment of a pre-customization unit 30 enabling to upload at least in part the transfer means 13 and/or the exploitations means to at least one blank unit 60 with the intention of obtaining a pre-customized unit 66. Said pre-customization unit 30 includes reading and writing means 31 enabling to electrically pre-customize, a blank unit 60 so as to obtain a pre-customized unit 66 to which the transfer means 13 and/or the exploitations means have been uploaded. The pre-customization unit 30 can also include physical customization means 32 of the blank unit 60 which can for instance, have the form of a printer. In the case where the unit 6 is constituted by a chip card 7 and its reader 8, the pre-customization generally concerns only the chip card 7.

[0584]FIG. 130 illustrates an embodiment of a system 35 enabling to carry out the making of the tools enabling to help generate protected software or to automate software protection. Such a system 35 includes a program development unit or workstation which has classically the form of a computer comprising a system unit, a screen, peripherals such as keyboard-mouse, and including, among others, the following programs: file editors, assemblers, pre-processors, compilers, interpreters, debuggers and link editors.

[0585]FIG. 140 illustrates an embodiment of a system 40 enabling to create directly a protected software 2 p or to modify a vulnerable software 2 v with the intention of obtaining a protected software 2 p. Such a system 40 includes a program development unit or workstation which has classically the form of a computer comprising a system unit, a screen, peripherals such as keyboard-mouse, and including, among others, the following programs: file editors, assemblers, pre-processors, compilers, interpreters, debuggers and link editors, as well as tools enabling to help generate protected software or to automate software protection.

[0586]FIG. 150 illustrates an embodiment of a customization unit 45 enabling to upload the second object part 2 pou to at least one blank unit 60 with the intention of obtaining at least one unit 6 or to upload a part of the second object part 2 pou to at least one pre-customized unit 66 with the intention of obtaining at least one unit 6. Said customization unit 45 includes reading and writing means 46 enabling to electrically customize, at least one blank unit 60 or at least one pre-customized unit 66, so as to obtain at least one unit 6. At the close of this customization, a unit 6 includes the information necessary to the execution of the protected software 2 p. The customization unit 45 can also include physical customization means 47 for at least one unit 6 which can for instance, have the form of a printer. In the case where a unit 6 is constituted by a chip card 7 and its reader 8, the customization generally concerns only the chip card 7.

[0587] The protection process according to the invention can be implemented with the following improvements:

[0588] It can be planned to use jointly several processing and memorizing units between which is divided out the second object part 2 pou of the protected software 2 p so that their joint use enables to execute the protected software 2 p, the absence of at least one of said processing and memorizing units preventing the usage of the protected software 2 p.

[0589] In the same way, after the pre-customization stage S₁₃ and during customization stage S₂₃, the part of the second object part 2 pou necessary to transform the pre-customized unit 66 into a unit 6 can be contained in a processing and memorizing unit used by the customization unit 45 so as to limit the access to said part of the second object part 2 pou. Naturally, said part of the second object part 2 pou can be divided out between several processing and memorizing units so that said part of the second object part 2 pou is accessible only during the joint use of said processing and memorizing units. 

What is claimed is: 1 - Process to protect, using at least one blank unit (60) including at least memorization means (15) and processing means (16), a vulnerable software (2 v) against its unauthorized usage, said vulnerable software (2 v) being produced from a source (2 vs) and working on a data processing system (3), said protection process comprising: during a protection phase (P): defining: at least one software execution characteristic, liable to be monitored at least in part in a unit (6), at least one criterion to abide by for at least one software execution characteristic, detection means (17) to implement in a unit (6) and enabling to detect that at least one software execution characteristic does not abide by at least one associated criterion, and coercion means (18) to implement in a unit (6) and enabling to inform the data processing system (3) and/or modify the execution of a software when at least one criterion is not abided by, constructing exploitation means enabling to transform the blank unit (60) into a unit (6) able to implement the detection means (17) and the coercion means (18), creating a protected software (2 p): by choosing at least one software execution characteristic to monitor, among the software execution characteristics liable to be monitored, by choosing at least one criterion to abide by for at least one chosen software execution characteristic, by choosing, at least one algorithmic processing which, during the execution of the vulnerable software (2 v), uses at least one operand and enables to obtain at least one result, and for which at least one chosen software execution characteristic, is to be monitored, by choosing at least one portion of the source of the vulnerable software (2 vs) containing, at least one chosen algorithmic processing, by producing the source of the protected software (2 ps) from the source of the vulnerable software (2 vs), by modifying at least one chosen portion of the source of the vulnerable software (2 vs) to obtain at least one modified portion of the source of the protected software (2 ps), this modification being such that: during the execution of the protected software (2 p) a first execution part (2 pes) is executed in the data processing system (3) and a second execution part (2 peu) is executed in a unit (6), obtained from the blank unit (60) after upload of information, the second execution part (2 peu) executes at least the functionality of at least one chosen algorithmic processing, and during the execution of the protected software (2 p), at least one chosen execution characteristic is monitored by means of the second execution part (2 peu) and the fact that a criterion is not abided by leads to a modification of the execution of the protected software (2 p), and by producing: a first object part (2 pos) of the protected software (2 p), from the source of the protected software (2 ps), said first object part (2 pos) being such that during the execution of the protected software (2 p), appears a first execution part (2 pes) which is executed in the data processing system (3) and whose at least a portion takes into account that at least one chosen software execution characteristic is monitored, and a second object part (2 pou) of the protected software (2 p), containing the exploitation means implementing the detection means (17) and the coercion means (18), said second object part (2 pou) being such that, after upload to the blank unit (60) and during the execution of the protected software (2 p), appears the second execution part (2 peu) by means of which at least one chosen software execution characteristic is monitored and by means of which the fact that a criterion is not abided by leads to a modification of the execution of the protected software (2 p), and uploading the second object part (2 pou) to the blank unit (60), with the intention of obtaining the unit (6), and during a usage phase (U) during which the protected software (2 p) is executed: in the presence of the unit (6): and as long as all the criteria corresponding to all the monitored execution characteristics of all the modified portions of the protected software (2 p) are abided by, enabling said portions of the protected software (2 p) to work nominally and consequently enabling the protected software (2 p) to work nominally, and if at least one of the criteria corresponding to a monitored execution characteristic of a portion of the protected software (2 p) is not abided by, informing the data processing system (3) of it and/or modifying the functioning of the portion of the protected software (2 p), so that the functioning of the protected software (2 p) is modified, and in the absence of the unit (6), in spite of the request by a portion of the first execution part (2 pes) to trigger the execution in the unit (6), of the functionality of a chosen algorithmic processing, in not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently, the protected software (2 p) is not completely functional. 2 - Process according to claim 1, to limit usage of a protected software (2 p), comprising: a during the protection phase (P): defining: as software execution characteristic liable to be monitored, a variable of measurement of the usage of a functionality of a software, as criterion to abide by, at least one threshold associated to each variable of measurement, and actualization means enabling to update at least one variable of measurement, constructing the exploitation means enabling the unit (6) to also implement the actualization means, and modifying the protected software (2 p): by choosing as software execution characteristic to monitor, at least one variable of measurement of the usage of at least one functionality of a software, by choosing: at least one functionality of the protected software (2 p) whose usage is liable to be monitored using a variable of measurement, at least one variable of measurement used to quantify the usage of said functionality, at least one threshold associated to a chosen variable of measurement corresponding to a limit of usage of said functionality, and at least one method of update of a chosen variable of measurement depending on the usage of said functionality, and by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that, during the execution of the protected software (2 p), the variable of measurement is actualized by means of the second execution part (2 peu) depending on the usage of said functionality, and at least one threshold crossing is taken into account, and during the usage phase (U), in the presence of the unit (6), and in the case where at least one threshold crossing corresponding to at least one limit of usage is detected, informing the data processing system (3) of it and/or modifying the functioning of the portion of the protected software (2 p), so that the functioning of the protected software (2 p) is modified. 3 - Process according to claim 2, comprising: during the protection phase (P): defining: for at least one variable of measurement, several associated thresholds, and different coercion means corresponding to each of said thresholds, and modifying the protected software (2 p): by choosing in the source of the protected software (2 ps), at least one chosen variable of measurement to which must be associated several thresholds corresponding to different limits of usage of the functionality, by choosing at least two thresholds associated to the chosen variable of measurement, and by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that, during the execution of the protected software (2 p), the crossings of the various thresholds are taken into account differently, by means of the second execution part (2 peu), and during the usage phase (U): in the presence of the unit (6): in the case where the crossing of a first threshold is detected, enjoining the protected software (2 p) not to use the corresponding functionality anymore, and in the case where the crossing of a second threshold is detected, making ineffective the corresponding functionality and/or at least one portion of the protected software (2 p). 4 - Process according to claim 2, comprising: during the protection phase (P): defining refilling means enabling to credit at least one software functionality monitored by a variable of measurement with at least one additional usage, constructing the exploitation means also allowing the unit (6) to implement the refilling means, and modifying the protected software (2 p): by choosing in the source of the protected software (2 ps), at least one chosen variable of measurement enabling to limit the usage of a functionality and which must be able to be credited with at least one additional usage, and by modifying at least one chosen portion, this modification being such that during a phase called of refilling, at least one additional usage of at least one functionality corresponding to a chosen variable of measurement can be credited, and during the phase of refilling: reactualizing at least one chosen variable of measurement and/or at least one associated threshold, so as to allow at least one additional usage of the functionality. 5 - Process according to claim 1, comprising: during the protection phase (P): defining: as software execution characteristic liable to be monitored, a profile of software usage, and as criterion to abide by, at least one feature of software execution, and modifying the protected software (2 p): by choosing as software execution characteristic to monitor at least one profile of software usage, by choosing at least one feature of execution by which at least one chosen profile of usage must abide, and by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that, during the execution of the protected software (2 p), the second execution part (2 peu) abides by all the chosen features of execution, and during the usage phase (U) in the presence of the unit (6), and in the case where it is detected that at least one feature of execution is not abided by, informing the data processing system (3) of it and/or modifying the functioning of the portion of the protected software (2 p), so that the functioning of the protected software (2 p) is modified. 6 - Process according to claim 5, comprising: during the protection phase (P): defining: an instructions set whose instructions are liable to be executed in the unit (6), a set of instructions commands for said instructions set, said instructions commands being liable to be executed in the data processing system (3) and to trigger in the unit (6) the execution of the instructions, as profile of usage, the chaining of the instructions, as feature of execution, an expected chaining for the execution of the instructions, as detection means (17), means enabling to detect that the chaining of the instructions does not correspond to the expected one, and as coercion means (18), means enabling to inform the data processing system (3) and/or to modify the functioning of the portion of protected software (2 p) when the chaining of the instructions does not correspond to the expected one, constructing the exploitation means also enabling the unit (6) to execute the instructions of the instructions set, the execution of said instructions being triggered by the execution in the data processing system (3), of the instructions commands, and modifying the protected software (2 p): by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that: at least one chosen algorithmic processing is split so that during the execution of the protected software (2 p), said algorithmic processing is executed by means of the second execution part (2 peu), using instructions, for at least one chosen algorithmic processing, instructions commands are integrated to the source of the protected software (2 ps), so that during the execution of the protected software (2 p), each instruction command is executed by the first execution part (2 pes) and triggers in the unit (6), the execution by means of the second execution part (2 peu), of an instruction, a sequence of the instructions commands is chosen among the set of sequences allowing the execution of the protected software (2 p), and the chaining by which must abide at least some of the instructions during their execution in the unit (6) is specified, and during the usage phase (U), in the presence of the unit (6), in the case where it is detected that the chaining of the instructions executed in the unit (6) does not correspond to the expected one, informing the data processing system (3) of it and/or modifying the functioning of the portion of the protected software (2 p), so that the functioning of the protected software (2 p) is modified. 7 - Process according to claim 6, comprising: during the protection phase (P): defining: as instructions set, an instructions set whose at least some instructions work with registers and use at least one operand with the intention of returning a result, for at least some of the instructions working with registers: a part (PF) defining the functionality of the instruction, and a part defining the expected chaining for the execution of the instructions and including bits fields corresponding to: an identification field of the instruction (CII), and for each operand of the instruction: a flag field (CD_(k)), and an expected identification field (CIP_(k)) of the operand, for each register belonging to the exploitation means and used by the instructions set, a generated identification field (CIG_(v)) in which is automatically memorized the identification of the last instruction which has returned its result in said register, as detection means (17), means enabling, during the execution of an instruction, for each operand, when the flag field (CD_(k)) imposes it, to check the equality of the generated identification field (CIG_(v)) corresponding to the register used by said operand, and the expected identification field (CIP_(k)) of the origin of said operand, and as coercion means (18), means enabling to modify the result of the instructions, if at least one of the checked equalities is false. 8 - Process according to one of the claims 1 to 7, comprising: during the protection phase (P): modifying the protected software (2 p): by choosing at least one variable used in at least one chosen algorithmic processing, which during the execution of the protected software (2 p), partially defines the state of the protected software (2 p), by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that during the execution of the protected software (2 p), at least one chosen variable or at least one copy of chosen variable resides in the unit (6), and by producing: the first object part (2 pos) of the protected software (2 p), said first object part (2 pos) being such that during the execution of the protected software (2 p), at least one portion of the first execution part (2 pes) takes also into account that at least one variable or at least one copy of variable resides in the unit (6), and the second object part (2 pou) of the protected software (2 p), said second object part (2 pou) being such that, after upload to the unit (6) and during the execution of the protected software (2 p), appears the second execution part (2 peu) by means of which at least one chosen variable, or at least one copy of chosen variable resides too in the unit (6), and during the usage phase (U): in the presence of the unit (6) each time a portion of the first execution part (2 pes) imposes it, using a variable or a copy of variable residing in the unit (6), so that said portion is executed correctly and that, consequently, the protected software (2 p) is completely functional, and in the absence of the unit (6), in spite of the request by a portion of the first execution part (2 pes) to use a variable or a copy of variable residing in the unit (6), not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently the protected software (2 p) is not completely functional. 9 - Process according to claim 6 comprising: during the protection phase (P): defining: as a triggering command, an instruction command, as a dependent function, an instruction, as an order, at least one argument for a triggering command, corresponding at least in part to the information transmitted by the data processing system (3) to the unit (6), so as to trigger the execution of the corresponding dependent function, a method of renaming of the orders enabling to rename the orders so as to obtain triggering commands with renamed orders, and restoring means (20) designed to be used in the unit (6) during the usage phase (U), and enabling to restore the dependent function to execute, from the renamed order, constructing exploitation means enabling the unit (6) to also implement the restoring means, and modifying the protected software (2 p): by choosing in the source of the protected software (2 ps), triggering commands, by modifying at least one chosen portion of the source of the protected software (2 ps) by renaming the orders of the chosen triggering commands, so as to conceal the identity of the corresponding dependent functions, and by producing: the first object part (2 pos) of the protected software (2 p), said first object part (2 pos) being such that during the execution of the protected software (2 p), the triggering commands with renamed orders are executed, and the second object part (2 pou) of the protected software (2 p) containing the exploitation means also implementing the restoring means (20), said second object part (2 pou) being such that, after upload to the unit (6) and during the execution of the protected software (2 p), the identity of the dependent functions whose execution is triggered by the first execution part (2 pes) is restored by means of the second execution part (2 peu), and the dependent functions are executed by means of the second execution part (2 peu), and during the usage phase (U): in the presence of the unit (6) and each time a triggering command with renamed order, contained in a portion of the first execution part (2 pes) imposes it, restoring in the unit (6), the identity of the corresponding dependent function and executing it, so that said portion is executed correctly and that, consequently, the protected software (2 p) is completely functional, and in the absence of the unit (6), in spite of the request by a portion of the first execution part (2 pes), to trigger the execution of a dependent function in the unit (6), not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that, consequently, the protected software (2 p) is not completely functional. 10 - Process according to claim 9, comprising: during the protection phase (P): defining for at least one dependent function, a family of dependent functions algorithmically equivalent, but triggered by triggering commands whose renamed orders are different, and modifying the protected software (2 p): by choosing, in the source of the protected software (2 ps) at least one triggering command with renamed order, and by modifying at least one chosen portion of the source of the protected software (2 ps) by replacing at least the renamed order of one chosen triggering command with renamed order, with another renamed order, triggering a dependent function of the same family. 11 - Process according to claim 10, comprising: during the protection phase (P), defining, for at least one dependent function, a family of algorithmically equivalent dependent functions: by concatenating a field of noise to the information defining the functional part of the dependent function to execute in the unit (6), or by using the identification field of the instruction (CII) and the expected identification fields (CIP_(k)) of the operands. 12 - Process according to claim 9, 10 or 11, comprising: during the protection phase (P): defining: as method of renaming of the orders, a ciphering method to cipher the orders, and as restoring means (20), means implementing a deciphering method to decipher the renamed orders and thus restore the identity of the dependent functions to execute in the unit (6). 13 - Process according to one of the claims 1, 2, 3, 4, 5, 6, 7, 9, 10 or 11, comprising: during the protection phase (P): modifying the protected software (2 p): by choosing, in the source of the protected software (2 ps), at least one conditional branch carried out in at least one chosen algorithmic processing, by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that during the execution of the protected software (2 p), the functionality of at least one chosen conditional branch is executed, by means of the second execution part (2 peu), in the unit (6), and by producing: the first object part (2 pos) of the protected software (2 p), said first object part (2 pos) being such that during the execution of the protected software (2 p), the functionality of at least one chosen conditional branch is executed in the unit (6), and the second object part (2 pou) of the protected software (2 p), said second object part (2 pou) being such that, after upload to the unit (6) and during the execution of the protected software (2 p), appears the second execution part (2 peu) by means of which the functionality of at least one chosen conditional branch is executed, and during the usage phase (U): in the presence of the unit (6) and each time a portion of the first execution part (2 pes) imposes it, executing the functionality of at least one conditional branch in the unit (6), so that said portion is executed correctly and that, consequently, the protected software (2 p) is completely functional, and in the absence of the unit (6) and in spite of the request by a portion of the first execution part (2 pes) to execute the functionality of a conditional branch in the unit (6), not being able to fulfill said request correctly, so that at least said portion is not executed correctly and that consequently, the protected software (2 p) is not completely functional. 14 - Process according to claim 13, comprising, during the protection phase (P), modifying the protected software (2 p): by choosing, in the source of the protected software (2 ps), at least one series of chosen conditional branches, by modifying at least one chosen portion of the source of the protected software (2 ps), this modification being such that during the execution of the protected software (2 p), the overall functionality of at least one chosen series of conditional branches is executed, by means of the second execution part (2 peu), in the unit (6), and by producing: the first object part (2 pos) of the protected software (2 p), said first object part (2 pos) being such that during the execution of the protected software (2 p), the functionality of at least one chosen series of conditional branches is executed in the unit (6), and the second object part (2 pou) of the protected software (2 p), said second object part (2 pou) being such that, after upload to the unit (6) and during the execution of the protected software (2 p), appears the second execution part (2 peu) by means of which the overall functionality of at least one chosen series of conditional branches is executed. 15 - Process according to one of the claims 1, 2, 3, 4, 5, 6, 7, 9, 10 or 11, comprising splitting the protection phase (P) into a prior protection sub-phase (P1), independent of the software to protect and a subsequent protection sub-phase (P2), dependent of the software to protect. 16 - Process according to claim 15, comprising, during the prior protection sub-phase (P1), making intervene a definitions stage (S11) during which are carried out all the definitions. 17 - Process according to claim 16, comprising, after the definitions stage (S11), making intervene a construction stage (S12) during which are constructed the exploitation means. 18 - Process according to claim 17, comprising, after the construction stage (S12), making intervene a pre-customization stage (S13), comprising uploading to a blank unit (60), at least a part of the exploitation means with the intention of obtaining a pre-customized unit (66). 19 - Process according to claim 16, comprising, during the prior protection sub-phase (P1), making intervene a tools making stage (S14) during which are made tools enabling to help generate protected software or to automate software protection. 20 - Process according to claim 18, comprising splitting the subsequent protection sub-phase (P2), into: a creation stage (S21) during which the protected software (2 p) is created, from the vulnerable software (2 v), possibly, a modification stage (S22) during which the protected software (2 p) is modified, and a customization stage (S23) during which: the second object part (2 pou) of the protected software (2 p) containing the exploitation means is uploaded to at least one blank unit (60) with the intention of obtaining at least one unit (6), or a part of the second object part (2 pou) of the protected software (2 p) possibly containing the exploitation means is uploaded to at least one pre-customized unit (66) with the intention of obtaining at least one unit (6). 21 - Process according to claim 20, comprising, during the creation stage (S21) and possibly during the modification stage (S22), using at least one tool which help generate protected software or which automate software protection. 22 - System for the implementation of the process in accordance with claim 17, characterized in that it includes a program development unit, used, during the construction stage (S12), to carry out the construction of the exploitation means intended for the unit (6), taking into account the definitions intervened during the definitions stage (S11). 23 - System for the implementation of the process in accordance with claim 18, characterized in that it includes a pre-customization unit (30) enabling to upload at least a part of the exploitation means to at least one blank unit (60), with the intention of obtaining at least one pre-customized unit (66). 24 - System for the implementation of the process in accordance with claim 19, characterized in that it includes a program development unit, used to carry out during the tools making stage (S14), the making of tools which help generate protected software or which automate software protection. 25 - System for the implementation of the process in accordance with claim 20, characterized in that it includes a program development unit used to create or modify a protected software (2 p). 26 - System for the implementation of the process in accordance with claim 20, characterized in that it includes a customization unit (45) enabling to upload: the second object part (2 pou) to at least one blank unit (60), with the intention of obtaining at least one unit (6), or a part of the second object part (2 pou) to at least one pre-customized unit (66), with the intention of obtaining at least one unit (6). 27 - Pre-customized unit (66), characterized in that it is obtained by the system in accordance with claim
 23. 28 - Unit (6) enabling to execute a protected software (2 p) and to prevent its unauthorized usage, characterized in that it contains the second object part (2 pou) of the protected software (2 p) uploaded using a customization unit (45) in accordance with claim
 26. 29 - Set of units (6), characterized in that the second object part (2 pou) of the protected software (2 p), uploaded using a customization unit (45) in accordance with claim 26, is divided out between several processing and memorizing units so that their joint use enables to execute the protected software (2 p). 30 - Distribution set (2 pd) of a protected software (2 p), characterized in that it includes: a first distribution part (2 pds) containing the first object part (2 pos) and designed to work in a data processing system (3), and a second distribution part (2 pdu) having the form: of a blank unit (60), or of a pre-customized unit (66), able after upload of customization information, to transform into a unit (6) in accordance with claim 28, or of a unit (6) in accordance with claim
 28. 31 - Distribution set (2 pd) of a protected software (2 p) according to claim 30, characterized in that the first distribution part (2 pds) has the form of a physical distribution medium, a CDROM for instance, or the form of files distributed through a network. 32 - Distribution set (2 pd) of a protected software (2 p) according to claim 30, characterized in that the second distribution part (2 pdu), having the form of blank units (60), of pre-customized units (66) or of units (6), includes at least one chip card (7). 33 - Processing and memorizing unit characterized in that it contains the part of the second object part (2 pou) necessary to transform a pre-customized unit (66) into a unit (6) in accordance with claim
 28. 34 - Set of processing and memorizing units characterized in that the processing and memorizing units used jointly, contain the part of the second object part (2 pou) necessary to transform a pre-customized unit (66) into a unit (6) in accordance with claim
 28. 